SAP ILM (IQ back end) after system refresh - missing ZILMSTORRD* objects in IQ
source link: https://answers.sap.com/questions/13852051/sap-ilm-iq-back-end-after-system-refresh-missing-z.html
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
SAP ILM (IQ back end) after system refresh - missing ZILMSTORRD* objects in IQ
We have SAP ILM connected to IQ databases across our landscape (Dev/QA/Prd) and all have been archiving to their respective IQ databases successfully. We have recently refreshed the QA NW stack from Prd and I am having issues getting ILM in QA working again.
Previous archive information was not required as part of the refresh so I have dropped the existing QA IQ database and provisioned a new one to avoid issues with broken logical links, etc.
Archive objects in NW have been deactivated, corresponding infostructures deleted, then reactivated. This did not generate the ZILMSTORRD* objects in IQ as I expected it would.
As a result archive jobs are failing at the store stage due to the objects being missing (a quick sp_iqdbspaceinfo shows there to be no object_names present)
I feel I'm very close to resolving but missing that last piece of the puzzle i.e. how are the ZILMSTORR* objects created and the required steps to resolve this.
I've been through all the Neenu Susan George and Roland Kramer blogs that I'm aware of but can't find this particular piece of information.
Could anybody please advise on what I'm missing?
thanks
Hello Steve,
Could you give more details on the exact error shown in the store job. Are you getting a "Table does not exist" error? You can also check transaction SLG1 for object ILM_STOR for the error logs.
Also, I understand that you now want to store new archive files into the IQ database, and do not want to access any older stored files. Is this understanding correct?
Best Regards,
Neenu
Hi Neenu,
This is the output from the store job
And the corresponding SLG1 output
In terms of landscape and usage, you are correct.
QA and PRD are as you would expect completely independent of one another so each has its own respective IQ server back end, table structure, licence, SID, system users, etc.
When planning the system refresh I'd reached agreement with our functional teams that previously archived information does not need to be accessible. If this had been a requirement I would have copied the PRD IQ files back to the QA IQ server but that presumably also brings with it complications at the IQ DB level when reconnecting everything.
The functional teams requirement is that they can test the archiving process in QA with new data from the refresh, rather than access data prior to the refresh.
Just spotted an ST22 dump for this highlighting the failure due to absence of the ZILMSTORRD* tables
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK