Description

Messages such as the following are seen in the Aleph 23 Oracle alert log:

• WARNING: too many parse errors, count=136 SQL hash=0x190d3f2c 

PARSE ERROR: ospid=8987, error=942 for statement: 
2020-01-02T09:28:25.147846-05:00 
select /*+ index(z410 z410_id3) */ * from xxx30.z410 where z410_id >= :v1 and z410_archive = 'N' 
Additional information: hd=0x68bc1d88 phd=0x68bc31b0 flg=0x28 cisid=79 sid=79 ciuid=79 uid=79 sqlid=cmyurz8chugtc 
...Current username=ALEPH 
...Application: pc_server_main@aleph23-prod (TNS V1-V3) Action: 

• WARNING: too many parse errors, count=141 SQL hash=0x46ab245f 

PARSE ERROR: ospid=8996, error=942 for statement: 
2020-01-02T11:23:17.492228-05:00 
select /*+ index(z700 z700_id) */ * from pwd50.z700 where z700_rec_key >= :v1 
Additional information: hd=0x67df9898 phd=0x67dfaff0 flg=0x28 cisid=79 sid=79 ciuid=79 uid=79 sqlid=awwjq913aq92z 
...Current username=ALEPH 

...Application: www_server_main@aleph23-prod (TNS V1-V3) Action: 

• WARNING: too many parse errors, count=1000 SQL hash=0x63376cc0 

PARSE ERROR: ospid=26654, error=942 for statement: 
2020-01-09T09:07:28.601092-05:00 
insert into xxx50.z00r values (:r1:i1,:r2:i2,:r3:i3,:r4:i4,:r5:i5) 
Additional information: hd=0x72edb9b8 phd=0x72593450 flg=0x100476 cisid=79 sid=79 ciuid=79 uid=79 sqlid=dsdk0q9jmfv60 
...Current username=ALEPH 
...Application: pc_server_main@aleph23-prod (TNS V1-V3) Action: 

In each case, these are tables which do not exist. What might be causing these errors and how can I address them?

Resolution

It seems that these started with the Oracle 12c/19c used by Aleph23.  You can just ignore the messages -- unless they seem to be connected to some actual problem.

If you want to eliminate the messages....

• As described in the "update_cursor3 z41x" errors article, z41n messages usually point to an incorrect line in the $alephe_tab/library_relation table.
• As described in the "Oracle error: update_cursor z700; ... table or view does not exist " article, z700 messages require the creation of a z700 table in the $pw_library.
• In the case of the xxxnn z00r, the problem can be that the ./xxxnn/tab/tab100 has this line: 

CREATE-Z00R=Y 

while the entries for the z00r in the ./xxxnn/file_list are commented out and the xxxnn.z00r table doesn't actually exist.   If the z00r is not needed/wanted in the xxxnn library, change the tab100 line to "CREATE-Z00R=N" (and restart the pc_server).   

• Article last edited: 8-Jan-2020