Skip to Content
author's profile photo Former Member
Former Member

upgrade error

Hi,

I got the following when i executed the command:

F:\>tp pf=F:\usr\sap\put\bin\DEFAULT.TPP execdbscript PRD -x SQLDBSCRIPT.TQL

sapparam: sapargv( argc, argv) has not been called.

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

This is tp version 340.07 (release 640)

Warning: Parameter INTERRUPT is no longer used.

Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.

Warning: Parameter WITH_TACOB is no longer used.

Warning: Parameter IMPDP_BY_EVENT is no longer used.

Warning: Parameter INTERRUPT is no longer used.

Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.

Warning: Parameter WITH_TACOB is no longer used.

Warning: Parameter IMPDP_BY_EVENT is no longer used.

Warning: Parameter DBNAME is no longer used.

Warning: Parameter DBHOST is no longer used.

Warning: Parameter DBCONFPATH is no longer used.

tp finished with return code: 0

meaning:

Everything OK

can u pls advice me how to resolve the issue.

regards,

kris

Add a comment
10|10000 characters needed characters exceeded

Related questions

6 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Nov 19, 2007 at 12:23 PM

    Dear,

    Are you executing the SQLDBSCRIPT.TQL manually ? or the tp call sent above has been started by the upgrade ?

    What is the source and target system versions ?

    Please send me more information about the upgrade status (phase and the last lines in upgdialog.log or scrolldialog.log)

    Regards,

    Lucio

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 19, 2007 at 06:18 PM

    Hi Rodrigues,

    Thanx for the reply.

    I have executed the command manually.

    I have a standalone system on which am doing the upgrade.

    The version is 4.7EE

    I am upgrading the system ECC 6.0

    Oracle version is 9.2.0.4.0 in the source system.

    scrolldialog.log details:

    >> 16:36:58 PREPARE: START OF PHASE PR_DBPAR

    SAPup error message

    SAPup> ERROR: during execution of script 'SQLDBSCRIPT.TQL'.

    Error found in logfile or standard output file.

    Check log files 'TPSQLSTD.OUT' and 'SQLDBSCRIPT.OUT'.

    - "continue"

    - "cancel"

    Enter one of these options [continue] := continue

    SAPup message

    SAPup> CHECKS AFTER PHASE PR_DBPAR WERE NEGATIVE !!!

    It is recommended that you repeat phase PR_DBPAR

    You can exit and restart the phase after the errors

    have been corrected. Alternatively, if you know that

    the error is not of concern, you may ignore it

    and continue with phase CHECKGROUP_END1

    You are urged to repeat phase PR_DBPAR !

    - "repeat"

    - "init"

    - "exit"

    - "ignore"

    Enter one of these options [repeat] := repeat

    pls help me to resolve the issue.

    Regards,

    kris

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 19, 2007 at 06:39 PM

    Dear,

    I see that you executed the "tp" command direct from "F:\>" check that the source kernel (source 6.40 TP) is being used for executing the script.

    The upgrade executes the script using the target system kernel (version 7.00), from (usr/sap/put/exe), the complete tp call is logged in file TPSQLSTD.OUT which contains further details about the failure.

    (maybe tp connect ?, database shared library load failure ? ). The answer for the phase failure should in this log.

    send us the contents of this file.

    Regards,

    Lucio Rodrigues

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 20, 2007 at 12:58 AM

    Hi Rodrigues,

    This is the content in the TPSQLSTD.OUT log

    SAPup> Starting subprocess tp.exe with id 1644 at 20051118174421

    EXECUTING F:\usr\sap\put\exe\tp.exe pf=F:\usr\sap\put\bin\DEFAULT.TPP execdbscript PRD -x SQLDBSCRIPT.TQL

    Environment: dbs_ora_schema=SAPPRD

    Environment: dbs_ora_tnsname=PRD

    Environment: NLS_LANG=AMERICAN_AMERICA.WE8DEC

    Environment: ORACLE_HOME=F:\oracle\ora92

    Environment: ORACLE_SID=PRD

    This is F:\usr\sap\put\exe\tp.exe version 370.00.09 (release 700)

    Process with ID 1100 terminated with status -1066598273

    Regards,

    kris

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 20, 2007 at 11:28 AM

    Dear Kris,

    We have observed the same issue when the new tp tool (7.00) terminates with the same issue (status -1066598273 ) due to a wrong database client software version . I strongly recommend to run the whole upgrade using the ORACLE 10g (NW04s products/tools are totally enabled for this database version, check the note 819655). In principle, you can still perform the preparation phase of the SAP application upgrade (=PREPARE-phase) with the Oracle 9i database. However, the actual SAP upgrade MUST be performed with the Oracle database 10g.

    Anyway, please ensure also that the ORACLE client 10.2 (instant client) is installed (which is compatible for kernel 7.00) and the client software used for the source kernel 6.40 is patched enough. Please check the steps SAP Note 836517 .

    I'm confident that the solution of this note will solve this issue.

    Regards,

    Lucio Rodrigues

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 21, 2007 at 08:57 AM

    Hi Kris,

    Please upgrade your oracle to 10G and try the oracle upgrade is mention in the upgrade guide.

    Regards,

    Iqbal

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.