Kbase P101800: What to do if Pro-to-XXX did not work
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
GOAL:
What to do if Pro-to-XXX did not work
GOAL:
How to debug a failing migration from Progress to a foreign Database
GOAL:
Steps to debug ProtoORA or ProtoMSS or ProtoODBC
FIX:
While filling the screen PROGRESS to <ORACLE/MSS/ODBC> Conversion screen, add in "other connect parameters" for the foreign database, the string:
-Dsrv qt_debug,EXTENDED
This will add precious information within the file "dataserv.lg" as per example
....
10:37:31 OCI call oopen <6> cc = 1
10:37:31 OCI call oparse <6> sqlcrc = 46181
10:37:31 SELECT /*+ ROWID(T0) */ USER#,NAME FROM sys.user$ T0
10:37:31 OCI call omru <6>
10:37:31 OCI call oopen <7> cc = 2
10:37:31 OCI call oparse <7> sqlcrc = 30407
10:37:31 SELECT /*+ ROWID(T0) */ OWNER#,NAME FROM sys.link$ T0
10:37:31 OCI call omru <7>
The last query sent to the foreign database failed and caused the Pro-to-XXX to stop prior to completion.
For the above sample the statement
SELECT OWNER#,NAME FROM sys.link$;
run within SQL*Plus failed with a permission error.