Ansicht
Dokumentation
12600 - Digest Number 1133
BAL Application Log Documentation PERFORM Short ReferenceThis documentation is copyright by SAP AG.
Digest Number 1133
Craig,In fact I didn't delete the SYS* catalog views. But the error came from another
reason - damaged cross-reference file. I had similar issue when upgrading a
machine from V4R5 to V5R2, and as I remeber I just called the program without
deleting those objects.
In our TST refresh procedure, we do delete those catalog views first, then
CRTDUPOBJ them from a backup library which was set up long time ago. So you may
have to try it yourself, or just delete them as Volker mentioned. It is a safe
solution for all the cases in my opinion.
Thank you,
Victor
_________________________________
Message: 13
Date: Wed, 14 Jan 2004 23:14:44 -0000
From: "sapbasisguy" <craig_welchZbradycorp.com>
Subject: Re: No Database Table exists message
Thanks, Did you actually have to delete the SYS* tables first? I
deleted them this time but I'd be interested in knowing if it was
necessary or not.
Craig.
--- In DoNotReply@consolut.eu, "Lin, Victor" <vlinZp...> wrote:
> Craig,
>
> The following command should fix the SYS* catalog views in
R3<SID>DATA library.
>
> CALL QSYS2/QSQXRLF PARM(CRT R3<SID>DATA)
>
> Last time I had this problem, the database cross-reference file was
damaged. So I had to do a "RCLSTG SELECT(*DBXREF)" too.
>
> Good luck,
> Victor
[Non-text portions of this message have been removed]
Durban Tours - Südafrika Safari
CPI1466 during Backup CL_GUI_FRONTEND_SERVICES - Frontend Services
This documentation is copyright by SAP AG.
Length: 2164 Date: 20240425 Time: 075724 sap01-206 ( 2 ms )
