on 09-16-2010 5:07 PM
While implementing ECC6 EHP4/NW701 Support Package Stack 7 we are getting the following error on Support Package SAPKNA7016
View CTSOBJLISTV could not be activated
(E- Table contains more than 3 long string fields )
Table CTSOBJLIST was activated (error in the dependencies)
Table CTSOBJLISTT was activated (error in the dependencies)
Table SI_RQ_CONTENT was activated (error in the dependencies)
Table CTS_FILEOBJECT was activated with warnings
(W- Field name FILE is reserved (Do not use structure as include in DB table) )
We have made no changes to this object.
The Support package note (822379) indicates SAPKB70108 shouild be incluided in the que along with SAPKB70105 - SAPKB70107 but SAPKB70108 is not available at service marketplace.
Has anyone seen and overcome this problem?
Thanks in advance.
Additional Information:
We activated ctsobjlist table and tried to activate the view ctsobjlistv which would not activate due to 4 long string fields.
We deleted the fourth string field called "additional info" and were able to activate the view with a warning.
SPAM was able to continue.
Question: What is the recomended way of handling this type of problem?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Since I was in a sandbox we were able to do something that is really not recommended. We deleted one of the Long String fields getting us down to the limit of three.
I have since applied the note to increase the number of long string fields allowed across my landscape and do not expect to see this problem when we go to DEV.
I was very disappointed that this was not referenced in the Support Package note we try to review before applying support package stacks.
Today I ran onto the same activation error for view CTSOBJLISTV with an SP for SAP_BS_FND. I am applying CRM 7.0 EHP1 SPS 3 to SPS 8. Implementation of SAPNote 1354957 solved the activation error and the queue runs again (import proper).
Thanks,
Rob.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello to all,
I´m facing with the same problem during an importing support packages process in SPAM! I´m applying CRM 7.0 EHP1 SPS 3 to SPS 8.
If you try to implement the note 1354957 (in snote) and you get the error message "OCS locked by user sapbasis with transaction SPAM", you have to do the manually corrections!
To correct this situation I did exactly what Anton Renberg recommended, which is the manual correction that you can find in note 1354957 (in section Corrections Instructions) on report RADTBCHK (in SE38). After this changes, don´t forget to do the activation to the program.
After all this procedures... you can continue/restart the importing support packages process.
Thank you very much!
Best regard,
João Dimas - Portugal
I did get the same error when applying SP stack 8 to CRM and it failed on DDIC Activation. I applied your solution by implementing the note changes manually (Note 1354957). The problem was solved and the SP import continued normally. Thanks a lot.
Muriel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello!
I'm importing SPS 7 in NW 7.0 with EhP1 (it was in SPS 3)
I get the same error: CTSOBJLISTV could not be activated
I read note "1354957 - Tables with more than 3 long string fields" and the support package SAPKB70105 that have this correction is in the queue but is next to the PI_BASIS SP 4 that have this error.
Now, how can I solve this issue?
Best regards,
Filipe
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just solved it by doing the note changes manually.
Very easy.
In program RADTBCHK
Delete Block
if nr <= 3. clear maxstrgnr.
else.
DT132: Table contains more than 3 long string-fields
perform stdo_smi0 using prid maxstrgnr(1) 'DT132'.
Insert Block
According to platform coordination meeting from 20050512, the restriction
for LOB columns is 16 per table definition. Pragmatically, this is a
simply evaluatable limit by counting the LOB columns, without deep
evaluation of the actual database platform limits.
- Initially, when introducing LOBs, 3 had been chosen due to then existing
platform limitiations.
See log: https://bis.wdf.sap.corp/twiki/Sapinternal/JdbcMinutes20050609#NumberOfLobs
on the modified limit 16.
- Confirmation to upgrade limit from 3 to 16 starting from SAP_BASIS 7.01 SP 05
by DB2/iSeries platform in Jun 09.
if nr <= 16. clear maxstrgnr.
else.
DT132: Table contains more than <n> long string-fields
perform stdo_smi1 using prid maxstrgnr(1) 'DT132' '16'.
We ran into the same issue our Development System. We fixed it using note 1354957.
For some reason we did not get this same error in our Sandbox system.
Note 1354957 has correction 1243983 which explains the fix for report RADTBCHK.
We exported report RADTBCHK from our Sandbox and imported into Development and we were able to continue.
Another option would be to apply the fix in correction 1243983 manually in report RADTBCHK.
Hope this helps....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
24 | |
11 | |
9 | |
7 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.