Product

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

Operating system

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

Error

[SERVERERROR] ORA-01012: not logged on

rw err = 5; db err #1 = 1012; db err #2 = 0; database service name = 'AraxiDBServer'; database user name = 'prinergy'

Symptoms

After you open a job, Prinergy Workshop closes or stops responding. The error message appears in the diagnostic log files from one or more Prinergy server daemons.

Cause

There are two possible causes:

• One of the build objects is incorrect, and may or may not be listed as corrupt. It may just contain incorrect data and not actually be invalid.
• There may be too many JTPs configured on one server, causing Windows to exhaust one or more resource pools. This problem is related to the DesktopHeap pool, which has a fixed size of 48 MB and cannot be increased. Each process on the primary server (including JTPs) uses a portion of memory from the DesktopHeap pool. When this pool is exhausted, processes will fail. Pjobd.exe will fail and report the ORA-01012 error. In this case, the error message is unrelated to Oracle. This problem should only occur in extreme circumstances, where there are 25 or more JTPs on one server. This can often occur with ColorMatcher and Vector Output JTPs, because the licensing for these features is not enforced.

Solution

First, determine the number of JTPs on the primary server. If the number seems large (25-plus), temporarily shut down a few JTPs to try and solve the problem. If that is the solution, redistribute JTPs to other servers, or remove them entirely (for example, very few sites require eight ColorMatch JTPs). If the problem persists, perform the following procedure.

1. Stop Prinergy.
2. Run the MakeBuildObjects SQL script on the database. )Modify the drive letters to suit the system configuration.)
3. Open a command-prompt window and type the following commands:
   C:\> cd %araxihome%\creoaraxi\setup\config\sql
C:\> sqlplus prinergy/araxi
SQL> @makebuildobjects.sql
SQL> commit;
SQL> exit

4. Restart Prinergy and test the system.

If this does not solve the problem, there may be a corrupt job in the database. Note very carefully which jobs were open at the time of the problem, and test them one by one until you find the corrupt job. After you locate it, recreate the job from scratch.

Keywords

Workshop

Technical contact(s)

Submitted by

Date submitted

09 Apr 2008