At least 2 connections are required - one for the repository database server and 1 or more for audited database servers. If you deal with a single database server, which is being audited and at the same time is used as a repository, both connections point to the same server. The log indicates only one successful connection. Please attach a screenshot or describe what you are entering for the connection parameters. You can mask user names and passwords, this is not important, I'm more concerned about the selected connection driver/method and the connection string format.

The Alert Center is unable to connect to the database with the specified parameters. Please correct the connection parameters and try again.

Tue Aug 18, 2009 4:41 am

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6571

jdbc:oracle:thin:@192.168.1.202:1521:DBAUDIT
This looks ok. The interface settings also look ok

I suggest 2 things - check if you have SQLNET.ORA, TNSNET.ORA or similar .ORA files in the Alert Center directory and subdirectories. If you find such files, open them in the Notepad, specific connection related errors should be reported in these files. They may help to identify the root cause of the problem and correct it.

If none of the above helps, please setup an ODBC connection for your Oracle database. When the Deployment Wizard or Alert Center Wizard in DB Audit Management Console prompt you for the repository connection, click ODBC option and then use [...] button to select the ODBC profile name.

Please let us know if this helps.

Tue Aug 18, 2009 9:01 am

sange

Joined: 14 Aug 2009Posts: 15Country: China

"listener.log" in the database server (192.168.1.202) as follows:

TNSLSNR for Linux: Version 10.2.0.1.0 - Production on 19-AUG-2009 11:50:26

Copyright (c) 1991, 2005, Oracle. All rights reserved.

System parameter file is /oracle/product/10.1.0/network/admin/listener.ora
Log messages written to /oracle/product/10.1.0/network/log/listener.log
Trace information written to /oracle/product/10.1.0/network/trace/listener.trc
Trace level is currently 0

Started with pid=1274
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.202)(PORT=1521)))
Listener completed notification to CRS on start

Also, please tell me the detailed steps for the deployment of DB Audit.

Wed Aug 19, 2009 1:38 am

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6571

Your LISTENER.ORA file indicates successful connections from both DB Audit Management Console and from the Alert Center. The Chinese environmental should be ok too. It must be then something else that is causing the issue, the process breaks in some other place, but from DB Audit Management Console point of view it fails while setting up new connection, which leads to misleading error message.

Here is what I suggest to try. Please configure manually 2 database connections in the Alert Center. Start the Alert Center scheduler GUI by using master.bat file, if it is not already running. Click Tools/Database Profiles menu. Select Oracle item and click the New button. Name the new profile exactly as it is named in the DB Audit GUI. For the connection parameters enter jdbc:oracle:thin:@192.168.1.202:1521:DBAUDIT user SYSTEM and password for that user. Click Test to test it and if ok, close the dialog. Click the New button again and repeat the same steps, but this time name the new connection profile as "Repository Server" without double quotes. After that DB Audit Management Console should be able to find the connections and do not prompt for them again. Hope this will solve the issue and will not create side effects.

Wed Aug 19, 2009 5:32 am

sange

Joined: 14 Aug 2009Posts: 15Country: China

In accordance with your suggest, the previous error is no longer prompted, I can choose to archiving scope and server whose audit trails will be saved in the repository, but in the "center" label, when prompted to "Creating required files and jobs ..." took place Error:

In the Alert center, create a new Alert, whether in the Repository Server or directly in the Audited Database Server, have taken place in "class java.lang.OutOfMemoryError" error.

Modify the parameters of jvm in master.bat also does not work.

Thu Aug 20, 2009 4:42 am

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6571

Ok, the 1 step manual setup for db connection didn't resolve the issue completely. Here are several additional steps you should do to workaround the connection issue.

1. Start Alert Center scheduler in the graphical mode as you did it before.
2. Click File->New->Job Queue menu. Enter name DBAUDIT and click OK
3. Click File->New->Folder menu. Enter name $DATABASE$ DBAUDIT, for the description enter the following exactly as it appears below

Code:

[ Do not modify this folder ]

DB TYPE: Oracle

4. Click OK.

Now try to use the Repository Deployment tool again. It should not complain about the connection anymore

Thu Aug 20, 2009 7:48 pm

sange

Joined: 14 Aug 2009Posts: 15Country: China

As you said, it is no longer an error to add alerts and reports with Repository Deployment tool.

However, if the use of Alert Center Remote Console to set up alerts and reports, and always took place "class java.lang.OutOfMemoryError" error.

If so, some alerts in the Repository Deployment tool could not be set, such as:
Data Changes in Certain Tables;
Access to Certain Tables After Regular Business Hours
And so on ...

How to solve this problem.

Thank you for so patiently.

Fri Aug 21, 2009 5:40 am

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6571

Where do you see "class java.lang.OutOfMemoryError" error? In the Alert Center log files or on the graphical Alert Center Remote Console? If you see this in some log file, in which one? and what appears above that error line?

Which version of JRE/JDK are you using to run the Alert Center? On the client?

Fri Aug 21, 2009 3:08 pm

sange

Joined: 14 Aug 2009Posts: 15Country: China

jdk/jre version 1.4.2_19, Alert Center Server and Client in the same host.

The error was not appear in the log files. In the Alert Center Remote Console, add or modify Alert or Report, pop-up message box displays the error.

Mon Aug 24, 2009 11:20 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6571

All right. So you get this error in the graphical console.

But when do you get it? When you use the New Alert Wizard? When you run that alert or something else?

Tue Aug 25, 2009 7:58 am

sange

Joined: 14 Aug 2009Posts: 15Country: China

When using the New Alert Wizard

Tue Aug 25, 2009 9:59 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6571

Let's try to gather more details. Please enable tracing option in the Alert Center scheduler. To enable this option, click Tools/Options menu in the Alert Center GUI, click Log tab and tick Trace Enabled checkbox, click OK to close Options dialog. In the Alert Center Remote Console reproduce the error (use New Alert Wizard). After that open debug.log file from the Alert Center installation directory and let us know last 10 lines from that file.