Jump to content


scminter

Member Since 30 Jun 2005
Offline Last Active May 10 2007 02:28 PM
-----

Posts I've Made

In Topic: Can you read a trace file?

16 June 2006 - 08:48 PM

I take slight offense. This is not my code, but standard Glovia 5.4.

They have two tables:

WO:

K CCN
K WO_NUM
K WO_LINE
WO_LAB_LASTSEQ

and

LAB_TIM:

K CCN
K MAS_LOC
K WO_NUM
K WO_LINE
K LAB_SEQ

Standard Glovia stores the value of the last labor sequence for a WO in the WO table. The consultant who created the customization basically started with a copy of Glovia's WOLTES function and modified it.

I added an SQL call to get the last seq from the table and increment before attempting the insert.

This design by Glovia could be a hold-over from when they were a flat file system. I do not know if it still exists in the current Glovia release.

In Topic: Can you read a trace file?

14 June 2006 - 12:45 PM

THANK YOU TO EVERYONE WHO HELPED ME WITH THIS ISSUE. (w00t)

Here is the final resolution:

A custom program was going into an infinite loop. At some point the Pro32srv service would run out of resources and stop. It would appear all of the other error messages I received were symptoms of this root cause. I modifed the program and the Pro32srv service has not crashed since. Nor have I received any further errors in my trace files.

More info:
The custom function was specific to Mitsubishi and automated labor entry. The function read the table WO to get the next sequence (key) to add to the file LAB_TIM. The insert failed and then the program looped forevever as it had no Error logics. I simply added an sql call in the before read to query the LAB_TIM table and get the last sequence; add one and then insert. Just in case, I added error logics as well.

In Topic: Can you read a trace file?

06 June 2006 - 05:50 PM

I found this in a trace file and have no idea what it means by "READ COMMAND ** DOES NOT EXIST **"

113705.095-OraCmdExec: Execute OK - rc = 0
113705.095-qgSqlFProc - FCB = 18FB1D0C, PFCB->FCRB = 00008004
113705.095-qgSqlFProc - NO TIB EXISTS
113705.095-qgSqlFProc: Open File and allocate new TIB
113705.095-qgStmCmp: exit TRUE, fMode1 0 fMode2 0 pFInst1 15892834 pFInst2 15892834
113705.095-qgSqlFOpen: tib 158D4070, pFcb 18FB1D0C, 'ODOM_OUT' -- Full Function
113705.095- Current ProIV function U_NXTVAL ls 1 fldno 68, curfile 1, 'ODOM_OUT'
113705.095-qgSqlFProc: FCB TIB = 158D4070
113705.095-qgPrmPreFSql: FULL FUNCTION COMMAND
113705.095-qgPrmPreRefs: ColumnReference ptr = 15892844
113705.095-qgSqlFProc: READ COMMAND **DOES NOT** EXIST
113705.095-qgStmCmp: XCPT_THROW (pStm1 != pStm2)

In Topic: Can you read a trace file?

05 June 2006 - 02:15 PM

That should have read 8.1.7.0.0. And maybe I'll just patch it up to 8.1.7.4 before I try to go to 9i.

Has anyone run Pro-IV kernel 4.6 5.2.3 (glovia) with Oracle 8.1.7.4 on windows?

In Topic: Can you read a trace file?

05 June 2006 - 12:57 PM

Oracle version is 8.1.0.0.

I'm thinking of upgrading to 9i. I believe the problem lies in the interaction between Oracle and the Pro-IV kernel, not in one of the Pro-IV programs. Since I need to upgrade to Oracle 9i anyway I'm thinking of giving it a shot. This may introduce more new problems however.