File QINLINE in library *LIBL not found or inline data

[Former Member]

Cause..: The file was not opened. The reason code is (3).

3 - The file does not exist. The library specified as *LIBL.

I believe this to apart of my issue using Tx SAINT and it being stuck on DDIC_IMPORT.

If anyone has any suggestions on what to do next that would be great. Thanks.

[Former Member]

Sorry for any confusion. This message comes from the TP joblog after a add-on installation terminated during phase DDIC_IMPORT within Tx SAINT. I am trying to do the EHP1 upgrade to Solution Manager and it is stuck trying to find a file within the buffer.

Since it's into the this phase I can't go back and clear the buffer... I'm pulling at string here trying to figure this one out.

I have looked through the /work directory for anything but didn't see any issues. So besides the joblogs and the /work dir I am unsure of where else to look.

Thank you for any help on this one.

[Former Member]

Hello Ryan

Could you paste the SLOG here to have more info, which you can find in /usr/sap/trans/log/SLOGxxxx.<SID>? Meanwhile, could you give me the result of command below:

qsh --> tp showbuffer <SID> pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.pfl tag=spam

With info above, we'll figure out what you're trying to import, in which phase, by what error it's stuck with.

Thanks,

Effan

[Former Member]

Hi Ryan,

I'm looking forward to the real solution ... but to me it sounds a bit strange and i would not be surprised when tp had a bug, that it tries to read some information from the keyboard, that is in a batch job not the best idea ...

I would open an OSS ticket on this ...

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

[Former Member]

I've got a customer message open with SAP currently; I was looking here for some other advice.

What I got back from your command was :

SMD buffer:

that makes 0 transports to be imported.

tp finished return code: 0

meaning:

Everything OK

I did check the SLOG and it had not been updated since 3/23. I had not started the upgrade before then, so I didn't think it applied.

I appreciate your responses.

Ryan

[Former Member]

Are you sure this is the right SLOG for this instance you're referring to? If SLOG is not updated, it means to me that there's no anything TP activity at all..... And how come you're having errors in phase DD import?

[Former Member]

Do you have any solution ?

I've got similar error during installation SM 7.0 Ehp1...

https://www.sdn.sap.com/irj/scn/forums

Regards

[Former Member]

Hi Ryan,

sorry, I do not understand what you are doing at all ... are you running SAINT ? I cannot believe this message there ...

I expect r3setup, r3up or sapup ... and there you need to OVRDBF qinline to the file you want to feed it with ...

Regards

Volker