7 Replies Latest reply: May 6, 2014 3:25 PM by Madhavi Kaza-Oracle RSS

    Siebel upgrep 7.8 SIA to 8.1.1.11

    1329826

      Ran the upgrep  siebel 7.8 SIA to  8.1.1.11 ,  the process finished successfully but as I was going through the state.log there were few errors flagged as high

      No mention on support web of any of these errors though

      I was wondering whether they can be ignored since the upgrep ran till the end

       

      Any input will be greatly appreciated , thanks.

       

      HSQLError Statement 0 0000000253640a6c:0 2014-05-03 06:50:39 SQL Statement: 70DROP INDEX S_LOY_PROD_PT_U1

       

      HSQLError Statement 0 0000000253641198:0 2014-05-03 08:26:27 SQL Statement: 70DROP INDEX S_LOY_PROD_PT_U1 SARMLog SARMInformation 3 0000000253641198:0 2014-05-03 08:26:27 SARM is OFF -change param SARMLevel to enable SARMLog SARMInformation 3 0000000253641198:0 2014-05-03 08:26:27 SARM Client is OFF -change param SARMClientLevel to enable SARMLog SARMInformation 3 0000000253641198:0 2014-05-03 08:26:27 SARM is OFF -change param SARMLevel to enable SARMLog SARMInformation 3 0000000253641198:0 2014-05-03 08:26:27 SARM Client is OFF -change param SARMClientLevel to enable SARMLog SARMInformation 3 0000000253641198:0 2014-05-03 08:26:27 SARM is OFF -change param SARMLevel to enable SARMLog SARMInformation 3 0000000253641198:0 2014-05-03 08:26:27 SARM Client is OFF -change param SARMClientLevel to enable

       

      HSQLError Statement 0 0000000253641148:0 2014-05-03 08:37:28 SQL Statement: 70DROP INDEX S_LOY_PROD_PT_U1 SARMLog SARMInformation 3 0000000253641148:0 2014-05-03 08:37:28 SARM is OFF -change param SARMLevel to enable SARMLog SARMInformation 3 0000000253641148:0 2014-05-03 08:37:28 SARM Client is OFF -change param SARMClientLevel to enable SARMLog SARMInformation 3 0000000253641148:0 2014-05-03 08:37:28 SARM is OFF -change param SARMLevel to enable SARMLog SARMInformation 3 0000000253641148:0 2014-05-03 08:37:28 SARM Client is OFF -change param SARMClientLevel to enable SARMLog SARMInformation 3 0000000253641148:0 2014-05-03 08:37:28 SARM is OFF -change param SARMLevel to enable SARMLog SARMInformation 3 0000000253641148:0 2014-05-03 08:37:28 SARM Client is OFF -change param SARMClientLevel to enable

       

      HSQLError Statement 0 00000002536410b4:0 2014-05-03 08:48:49 SQL Statement: 150insert into S_AUDIT_JOIN (ROW_ID ,CREATED ,CREATED_BY ,LAST_UPD ,LAST_UPD_BY ,CONFLICT_ID ,MODIFICATION_NUM ,AUDIT_BC_ID ,JOIN_NAME ,JOIN_SPEC_NAME ,SRC_COL_NAME ,SRC_TBL_NAME ) select case when length(JS.ROW_ID || AB.ROW_ID) < 16 then JS.ROW_ID || AB.ROW_ID else JS.ROW_ID || substr(AB.ROW_ID, length(AB.ROW_ID) - 15 + length(JS.ROW_ID), 15 - length(JS.ROW_ID)) end ,AB.CREATED ,AB.CREATED_BY ,AB.LAST_UPD ,AB.LAST_UPD_BY ,AB.CONFLICT_ID ,AB.MODIFICATION_NUM ,AB.ROW_ID ,J.NAME ,JS.NAME ,SC.NAME ,ST.NAME from S_AUDIT_BUSCOMP AB , S_BUSCOMP B , S_JOIN J , S_JOIN_SPEC JS , S_FIELD F , S_TABLE ST , S_COLUMN SC , S_REPOSITORY R where R.ROW_ID = B.REPOSITORY_ID and R.ROW_ID = ST.REPOSITORY_ID and R.NAME = 'Prior Customer Repository' and AB.BUSCOMP_NAME = B.NAME and B.TABLE_NAME = ST.NAME and B.ROW_ID = J.BUSCOMP_ID and J.ROW_ID = JS.JOIN_ID and B.ROW_ID = F.BUSCOMP_ID and JS.SRC_FLD_NAME = F.NAME and ST.ROW_ID = SC.TBL_ID and F.COL_NAME = SC.NAME and F.JOIN_NAME is null and exists (select 'x' from S_AUDIT_FIELD AF where AF.JOIN_NAME = J.NAME and AF.AUDIT_BC_ID = AB.ROW_ID ) 
        • 1. Re: Siebel upgrep 7.8 SIA to 8.1.1.11
          Madhavi Kaza-Oracle

          Hi,

           

          Thank you for posting your question to communities.

           

          I am unable to see the actual error that you encountered during upgrade based on the above rows from summary file.

           

          What steps does state.log file show as errored?

           

          For S_LOY_PROD_PT_U1 index, does it show index as not existing? sometimes this may turn out to be acceptable error depending on the context.

           

          Hence, please send your upgwiz*.log files so that we can take a look at the errors that you encountered.

           

          Thanks,

          Madhavi

          • 2. Re: Siebel upgrep 7.8 SIA to 8.1.1.11
            1329826

            Thanks for the prompt reply

             

            here's where it failed

             

            SQLErrorStatement00000000253641148:02014-05-03 08:37:28SQL Statement:

              DROP INDEX S_LOY_PROD_PT_U1

             

             

            DBCLogDBCLogError10000000253641148:02014-05-03 08:37:28[tp][ODBC Oracle driver][Oracle]ORA-01418: specified index does not exist

             

             

             

             

            UpgradeLogUpgradeError10000000253641148:02014-05-03 08:37:28[tp][ODBC Oracle driver][Oracle]ORA-01418: specified index does not exist

             

             

             

             

            UpgradeLogUpgradeError10000000253641148:02014-05-03 08:37:28Error in function UTLOdbcExecDirectDDL

             

             

            UpgradeLogUpgradeError10000000253641148:02014-05-03 08:37:28Error executing sql statement (

             

             

            DROP INDEX S_LOY_PROD_PT_U1).

             

             

            UpgradeLogUpgradeError10000000253641148:02014-05-03 08:37:28Error executing statement (RUN_SQL_70) in file (pret_sia.sql).

             

             

            UpgradeLogUpgradeInfo30000000253641148:02014-05-03 08:37:28Close database connection.

             

             

            UpgradeLogUpgradeError10000000253641148:02014-05-03 08:37:28Execute SQL file action failed.

             

             

            UpgradeLogUpgradeError10000000253641148:02014-05-03 08:37:28Error executing action (Prepare for table creation SIA).

             

             

            UpgradeLogUpgradeInfo30000000253641148:02014-05-03 08:37:28Status Message (Errors encountered)
            • 3. Re: Siebel upgrep 7.8 SIA to 8.1.1.11
              1329826

              I uploaded  four log files, three of them for SQL 70 and the fourth for SQL 150

               

              Thank you

              • 4. Re: Siebel upgrep 7.8 SIA to 8.1.1.11
                Madhavi Kaza-Oracle

                Thanks for sending the log files. I have noticed the following errors

                 

                1) from UpgWiz_04.log

                 

                UpgradeLog    UpgradeInfo    3    0000000253641100:0    2014-05-03 08:40:25    Executing SQL statement RUN_SQL_80:

                 

                ALTER TABLE S_LOY_PROD_PT

                 

                ADD  PROD_PT_UID VARCHAR2(15)

                 

                SQLError    Statement    0    0000000253641100:0    2014-05-03 08:40:25    SQL Statement:

                  ALTER TABLE S_LOY_PROD_PT  ADD  PROD_PT_UID VARCHAR2(15)

                 

                DBCLog    DBCLogError    1    0000000253641100:0    2014-05-03 08:40:25    [tp][ODBC Oracle driver][Oracle]ORA-01430: column being added already exists in table

                 

                 

                UpgradeLog    UpgradeError    1    0000000253641100:0    2014-05-03 08:40:25    [tp][ODBC Oracle driver][Oracle]ORA-01430: column being added already exists in table

                 

                 

                UpgradeLog    UpgradeError    1    0000000253641100:0    2014-05-03 08:40:25    Error in function UTLOdbcExecDirectDDL

                 

                UpgradeLog    UpgradeError    1    0000000253641100:0    2014-05-03 08:40:25    Error executing sql statement (

                 

                ALTER TABLE S_LOY_PROD_PT

                 

                ADD  PROD_PT_UID VARCHAR2(15)).

                 

                2) from upgwiz_09.log

                 

                DROP INDEX S_LOY_PROD_PT_U1

                 

                DBCLog    DBCLogError    1    0000000253641148:0    2014-05-03 08:37:28    [tp][ODBC Oracle driver][Oracle]ORA-01418: specified index does not exist

                 

                 

                UpgradeLog    UpgradeError    1    0000000253641148:0    2014-05-03 08:37:28    [tp][ODBC Oracle driver][Oracle]ORA-01418: specified index does not exist

                 

                ============

                 

                After this the upgrade process terminated and did not continue. It means that the errors are not acceptable.

                 

                Given that upgrade was looking for the index (in the upgrade path you are using) and was failing as it does not exist, did you run upgrade more than once without doing a proper restore of DB from backup?

                 

                For example - did you run the process first time and deleted SiebSrvr\Log directory for any reason and started the upgrade?

                 

                In which case, the process will start from beginning and will fail if the required index does not exist as upgrade already dropped it before.

                 

                This also coincides with the other error that I see - "ORA-01430: column being added already exists in table"

                 

                In this case, I suggest the following

                 

                1) Restore the DB from backup

                2) REmove/Rename SiebSrvr\Log directory

                3) Perform all pre-upgrade tasks that you earlier

                4) Run the UpgRep again.

                 

                If there is any thing else, I missed here, please let me know.

                 

                Thanks,

                Madhavi.

                • 5. Re: Siebel upgrep 7.8 SIA to 8.1.1.11
                  1329826

                  Actually the upgrep continued until the end , until  the Process Complete message

                   

                  Thanks!

                  • 6. Re: Siebel upgrep 7.8 SIA to 8.1.1.11
                    1329826

                    Madhavi


                    Since the upgrep did complete , would it be safe to move on with merge ?

                    • 7. Re: Siebel upgrep 7.8 SIA to 8.1.1.11
                      Madhavi Kaza-Oracle

                      Hi,

                       

                      The log files UpgWiz*.log tell otherwise, that there was indeed a problem.

                       

                      Please open a Service Request and provide all the upgrade log files including your state.log file.

                       

                      We should verify all the log files.

                       

                      At this point, I cannot recommend that you continue with the next steps due to the above errors.

                       

                      Thanks,

                      Madhavi.