IMPORT_PROPER PHASE ERROR

[former_member274353]

HI ,

During spam/saint upgrade showing error in phase import_proper any bdy help .

[manumohandas82]

Please check the following Note as suggested earlier  .

1913676 - Troubleshooting guide for Support Package / Add-Ons Installations errors during the main i...

You will either have to restore the database to a time before the SPAM update / Transport  it from another system as detailed in the Note

[manumohandas82]

Hi Sandeep ,

Please traverse to /usr/sap/trans/log  and post your ALOG and SLOG also the transport logs for the transport number SAPKD7408

Thanks ,

Manu

[Former Member]

Hi Sandeep,

Also do confirm if you have RDDIMPDP job running successfully in system. and along with this tp & R3trans version are updated.

Regards,

Ram

[former_member274353]

Hi ,

I have Updated Latest kernel and successfully run Job RDDIMPDP and attached SLOG and ALOG ,

I have attached rar file .

log.rar.txt.zip

[manumohandas82]

Hi Sandeep ,

The files attached  does not contain ALOG or SLog files . Take the last 100 lines formeach of the file and post it in a text file and attach the same .

Meanwhile check the following Note ( Under section Syntax Errors with object CL_OCS_RT_ANALYSIS )

1913676 - Troubleshooting guide for Support Package / Add-Ons Installations errors during the main im...

Thanks ,

Manu

[former_member189797]

Hi,

I checked the attached logs and could see in log SAPID* log that error code was 16 . So definitely it was not successful. Reason of the isuse was that "ASE has run out of locks". So you have to simply
increase the limit and repeat the database.

BR,
Gaurav

[former_member274353]

HI Gaurav ,

I am new sybase datbase please advise hot to incease the limit of ase

[former_member274353]

HI Gaurav ,

I have checked current lock in my data base . so please advise how much i will have to increase the locks attached screen shoot

[former_member189797]

Hi Sandeep,

This was the error which was faced originally with SPAM/SAINT update and will not help with dump since you already reset the SPAM/SAINT update. Like I mentioned earlier, force reset is never a good option and there are many reasons for that .

Since you have already used the force mode reset, I would recommend the below approach.

1. Restore the system to a state before you started the SPAM/SAINT update.
2. Apply the SPAM/SAINT update. You might face the same error as earlier so you can use Note 1884582 to increase the locks by 10-25 % of current value.

Once SPAM/SAINT is updated, you can do further patching.

Thanks.

BR,
Gaurav

[former_member274353]

HI ,

I have recently  install currently there is no backup without restore not possible resolved the issue

[former_member189797]

Hi Sandeep,

I would try to help but there is no gurantee that we would be able to fix all inconsistencies.
For now , please first finish the SPAM/SAINT import. Are you able to access the SPAM/SAINT transaction and start the SPAM/SAINT update again?

In case you face the same dump that transformation is not active then activate this in STRANS and try to start the SPAM/SAINT update.

In short, first import the SPAM/SAINT update "COMPLETELY" before doing anything on system.

Regards,
Gaurav

[former_member274353]

Dear Gaurav ,

How to activate transformation please can  you guide us

[former_member189797]

Hi Sandeep,

As I mentioned , use STRANS transaction to activate . Just make sure that there is no syntax error or you will not be able to activate it.

Regards,
Gaurav

[former_member274353]

Hi Gaurav ,

I have opened STRANS transaction  but i am not able to understand which transformation will have to put pls help .

[former_member189797]

Hi Sandeep,

You can find the transformation name in syntax error screenshot. Its RTA_SLANA .

BR,

Gaurav

[former_member274353]

HI Gaurav  ,

I have try but showing does not exist

[Former Member]

Hello Sandeep,

Its very easy to resolve that problem.. dont try to activate transformation and all..

Do you have any other system which is already updated SPAM version to 58?

Please confirm.

Regards,

KK

[former_member274353]

HI ,

IN windows system Yes I have

[Former Member]

Then there will be cofile and data file generated in directories /usr/sap/trans/cofiles and /usr/sap/trans/data with name K74058.SAP and R74058.SAP

So copy the both files to corresponding locations to target system which you are getting error...

after that add the TR SAPK74058 to import buffer in STMS_IMPORT --> Extra (in menu)--> Add give TR as SAPK74058 and then import it manually.... Once TR will imported successfully or with warnings... Then try to execute to SPAM... It will work..

I had faces same SYNTAX_ERROR issue.. so i did this only and it worked for me.

Regards,

KK

[former_member189797]

Hi Sandeep,

1. Do not force reset the queue. SPAM do not allow you to reset the queue in this phase and there is a reason why this feature is stil there. Without proper handling, this can destroy your system. This is not a solution and also this is not supported by SAP.

2. Please check the Note, 1912676 , which provides more information about what kind of issues can occur in import_proper phase and how they should be handled.

In case you still are not able to resolve the issue, we would need more details to help you further.
Screenshot is just not enough to help here.

Thanks.

BR,
Gaurav

[former_member274353]

HI ,

I have restart the whole system after restart checked spam status green and try again other support package but showing error

[former_member189797]

Hi Sandeep,

You mentioned that you restarted the system, and SPAM was green. A restart will not do this.
Was queue resetted with OCS_RESET_QUEUE in import_proper phase?

From the dumps, it says transformation is not active. however such thisng should not happen. This only happens due to aborted update attempt.

So I have few queries here.

1. What were the packages which you were trying to update in last attempt ?
2. How was issue in IMPORT_PROPER solved (How did SPAM become green).
3. Are packages in last queue already imported ?
4. What are the package in new queue which is being imported now ?

Thanks.

Best Regards,
Gaurav Pandey
SAP Product Support

[Former Member]

Hello Dear,

Kindly reset the SPAM Queue and the try again and if possible restart OS.

To reset the queue go to SE37->put the  OCS_RESET_QUEUE->Execute.

Then Put the value IV_TOOL=SPAM

                            IV_FORCE=X

Also check the SAP Note 822379.

If any, Let me know.

Thanks

Santosh Dwivedi

[Former Member]

@Santosh,

This a not recommended way by SAP to reset the queue unless and untill its must.

So Sandeep try to fix it based on the error your seeing lot of recommendations will come up based on the logs.

So sandeep do update us if your still seeing issue and update us on the logs too.

Regards,

ram

[Former Member]

Dear Ramkrishna,

I had already faced this issue earlier and resole it by as marked solutions.

For reseting of OCS queue also marked in sap note 822379.

You can check.

Regards

Santosh

[Former Member]

Hi Sandeep,

Can you pl share the logs for the same..

Kind Regard's

Mirza Ismail.

[Former Member]

hi Sandeep,

Can you paste the Action logs from the SPAM tcode. you can see a spool icon to access the same.

Based on the error then we will be able to guide.

regrds,

Ram

[former_member274353]

HI Ramkrishna ,

As required attached action log file

[Former Member]

Hi Sandeep,

Kindly Upgrade SPAM version 58 first and then go to next patches....

Regard's

Mirza Ismail.

[Former Member]

Hello Sandeep,

As error coming in log file.

First upgrade the SPAM/SAINT version at level of 58 and above then try.

Regards

Santosh Dwivedi

[former_member274353]

Hi Santosh ,

This error coming in spam/saint version same

[Former Member]

Hi Sandeep,

You mean while importing SPAM update also error coming like mark log?

[former_member274353]

HI ,

Yes ,

[former_member274353]

Hi SANTOSH ,

BUT SPAM STATUS GREEN WITH LATEST VERSION I HAVE ALREADY SHARE THIS SCREEN

[Former Member]

Hi Sandeep,

Once againg i checked your error log image.

This seems update not imported properly and uoy reset the queue forcefully.