![]()
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
||
Product |
Prinergy 1.1; Prinergy Connect 2.0 | |
Platform |
||
Operating system |
||
|
|
||
Error |
||
|
|
||
Symptoms |
An error similar to the following appears in DiagView: A general database failure has occured: [INVALIDPOSITION] Invalid position within RWDBStoredProc DBCS_GetLatestSchemaVersion. The stored procedure name (DBCS_GetLatestSchemaVersion in this example) may vary. Depending upon the stored procedure at fault, Prinergy may exhibit different symptoms, such as failure to import impositions, display history, or register files. |
|
|
|
||
Cause |
The stored procedure did not compile. The status of the procedure can be seen by issuing an SQL query similar to this: select status from user_objects where object_name like 'DBCS_GetLatestSchemaVersion'; Replace the stored procedure name 'DBCS_GetLatestSchemaVersion' with the stored procedure in error. The status will show 'INVALID' if the stored procedure did not compile. |
|
|
|
||
Solution |
Recompile all objects in the Prinergy database with the status of INVALID. In Prinergy 1.1 systems: 1) Start PLUS80 in a command prompt window. D:\> PLUS80 araxi_1_0_12/araxi 2) In PLUS80, execute the stored procedure DBCS_CompileObjects SQL> execute dbcs_compileobjects; 3) Exit PLUS80 SQL> exit In Prinergy 2.0 systems: 1) Start SQLPLUS in a command prompt window. D:\> SQLPLUS prinergy/araxi 2) In SQLPLUS, execute the stored procedure DBCS_CompileObjects SQL> execute dbcs_compileobjects; 3) Exit SQLPLUS. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
oracle |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
||