Product

Kodak^® Prinergy^® Connect^™, version 4.x

Operating system

• Microsoft^® Windows^® 2000 Server
• Microsoft Windows Server^® 2003

Error

On a very busy system, a customer may encounter an ORA-04031 error in the Prinergy log files. The text of the error message varies, but ORA-04031 always appears in it.

Symptoms

The ORA-04031 error appears in the Prinergy log files.

Cause

The Oracle^® 10g software is out of System Global Area memory and Program Global Area memory.

Solution

Increase the System Global Area memory and Program Global Area memory as needed.

Caution: Do this procedure only if the ORA-04031 error occurs, because the procedure causes Oracle to consume significantly more system random access memory (RAM), which may cause resource shortages on smaller systems.

1. Shut down Prinergy.
2. In a text editor, open the \oracle\10.2.0\database\initaraxi.ora file and make the following changes:

#shared_pool_size = 150M
sga_target = 200M
sga_max_size = 300M
#pga_aggregate_target = 50M
pga_aggregate_target = 200M

3. Save the file.
4. Locate %araxihome%\CreoAraxi\Setup\Config\Sql\Trigger and perform these steps:
1. Rename the DBCS_DatabaseInstanceTriggers.sql file to DBCS_DatabaseInstanceTriggers.sql.old.
2. Save this new file in the Trigger folder: DBCS_DatabaseInstanceTriggers.sql
5. Run the following SQL command to load the DBMS_SHARED_POOL package that is included with the Oracle 10g software:

C:\>sqlplus sys/creo
SQL>@\Oracle\10.2.0\RDBMS\ADMIN\DBMSPOOL.SQL

6. Run the following SQL command to load the new DBCS_DatabaseInstanceTriggers.sql file:

C:\>sqlplus prinergy/araxi
SQL>@%araxihome%
\CreoAraxi\Setup\Config\Sql\Trigger\DBCS_DatabaseInstanceTriggers.sql
SQL> commit;

7. Restart the Oracle services or restart the server.

Keywords

Oracle

Technical contact(s)

Submitted by

Date submitted

05 Feb 2008