1. Error
While integrating Siebel 8.1.1.9 with BI publisher 11g. In step of repatching Siebel_Reports in Siebel 8.1.1.9, ran into EIM tables ('EIM_XMLP_RPOUT' and 'EIM_XMLP_RPTMP' ) error.
The command running is
%TOOLSPATH%\BIN\siebdev.exe /c tools.cfg /d %DATASRC% /u %USERNAME% /p %PASSWORD% /batchimport "Siebel Repository" merge "%TOOLSPATH%\REPPATCH\Siebel_Reports\REPOSITORY\Tables\EIM Tables" "%TOOLSPATH%\LOG\EIMTables.log"
and it gave the below error,
Comparing import objects with repository objects ...
Checking that projects are already locked ...
Applying changes to repository at 06/24/13 04:43:40
Resolving foreign keys on object: Project 'EIM XMLP'
-> unknown object: 'Locked By Name' property refers to: VKUNHIPU
Resolving foreign keys on object: Table 'EIM_XMLP_RPOUT' of Project 'EIM XMLP'
Resolving foreign keys on object: Table 'EIM_XMLP_RPTMP' of Project 'EIM XMLP'
-> unknown object: 'User Key Attribute Name' property refers to: User Key Attribute 'SOURCE_TYPE_CD' of User Key 'S_XMLP_REP_IOBJ_U1' of Table 'S_XMLP_REP_IOBJ'
!!ERROR::Unable to find requested object 'User Key Attribute' 'SOURCE_TYPE_CD'
Cause:
1. In EIM tables repository import under table ''S_XMLP_REP_IOBJ' with user Key 'S_XMLP_REP_IOBJ_U1' it is searching for user key attribute SOURCE_TYPE_CD, where it actually exists with name 'SOURCE_TYPE'
2. Error.
Try to import PublicReportService_v11.wsdl
into Siebel as new web service(Page 16 in above doc), it gave the below error.
ObjMgrBusCompLog Error 1 0000000251d61a1c:0 2013-07-05 01:31:37 (buscomp.cpp (33489)) SBL-DAT-00225: The value entered in field Integration
Object of buscomp Repository Business Service Method Arg does not match any value in the bounded pick list Repository PickList Integration Object.
ObjMgrLog Error 1 0000000251d61a1c:0 2013-07-05 01:31:37 (adptutils.cpp (6867)) SBL-EAI-04451: Method 'SetFieldValue' of business component
'Repository Business Service Method Arg' (integration component 'Repository Business Service Method Arg') for record with search specification '[Name] = "logoutRequest:parameters"' returned the following error:"The value entered in field Integration Object
of buscomp Repository Business Service Method Arg does not match any value in the bounded pick list Repository PickList Integration Object.(SBL-DAT-00225)"
From Oracle support, I got one article "Why are SBL-EAI-04451 errors reported with the SetFieldValue method when the PublicReportService_v11.wsdl
is imported ? [ID 1051121.1]". Then I followed doc to delete PublicReportService Business Service and Integration Objects from the 'XMLP Integration' project in other repositories, but problem is still there.
Solution
1) Delete the business service PublicReportService and all
related integration objects from XMLP Integration project.
2) Also delete the old PublicReportService web service declaration in the Siebel GUI (Outbound Web Services).
3) Check the orphan records based on the SQL Statements:
SELECT * FROM SIEBEL.S_WS_OPERATION WHERE PROXY_NAME ='PublicReportService';
SELECT * FROM SIEBEL. S_WS_PORT_OPER WHERE OPERATION_ID IN
(SELECT ROW_ID FROM SIEBEL.S_WS_OPERATION WHERE PROXY_NAME ='PublicReportService');
SELECT ROW_ID, NAME FROM SIEBEL.S_RT_SVC WHERE NAME = 'PublicReportService';
Not work using above solution to delete all the records found with SQL.
1) Please delete multiple repositories and make sure that only one repository exists and then try to import the WSDL into Siebel Tools.
Worked
In EIM tables repository import under table ''S_XMLP_REP_IOBJ' with user Key 'S_XMLP_REP_IOBJ_U1' it is searching for user key attribute SOURCE_TYPE_CD
1) Please delete multiple repositories and make sure that only one repository exists and then try to import the WSDL into Siebel Tools.
I have tried the instructions in the following SR(Error During Upgrep - Cannot Create Unique Index; Duplicate Keys Found [ID 1360199.1]), that did not help solve the issue -
1. There were more than 2300 hundred records returned in the query
2. All of them were updated as CONFLICT_ID = 1
3. There were greater than 2 records with the combination of the UK from Siebel 8.1.1 -
The SQL used to Select the duplicate rows was:
Select NAME, DESC_TEXT, CONFLICT_ID,OWNER_ID,LANG_ID from (
SELECT NAME, DESC_TEXT, CONFLICT_ID,OWNER_ID,LANG_ID,COUNT(*)
FROM SIEBEL.S_APP_QUERY
GROUP BY NAME, DESC_TEXT, CONFLICT_ID,OWNER_ID,LANG_ID
HAVING COUNT(*) > 1
Order by DESC_TEXT ASC)
**************************************
create unique index S_APP_QUERY_U1 on S_APP_QUERY
("NAME", "DESC_TEXT", "OWNER_ID", "LANG_ID", "CONFLICT_ID")
tablespace SIEBEL_IX
2013-04-19 02:27:27 [tp][ODBC Oracle driver][Oracle]ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
2013-04-19 02:27:27
2013-04-19 02:27:27 S1000: [tp][ODBC Oracle driver][Oracle]ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
2013-04-19 02:27:27
2013-04-19 02:27:27 Dropping index with the same column signature and retrying...
2013-04-19 02:27:27 create unique index S_APP_QUERY_U1 on S_APP_QUERY
2013-04-19 02:27:27 ("NAME", "DESC_TEXT", "OWNER_ID", "LANG_ID", "CONFLICT_ID")
2013-04-19 02:27:27 tablespace SIEBEL_IX
2013-04-19 02:27:27
2013-04-19 02:27:27 ;
2013-04-19 02:27:27 writeExecDDL error (pOperCallback UTLDbDdlOperIndCreate).
2013-04-19 02:27:27 Error in MainFunction (UTLDbDdlDbMerge).
2013-04-19 02:27:27 Error in Main function...
2013-04-19 02:27:27 (logapi.cpp (184) err=1 sys=0) SBL-GEN-00001: (logapi.cpp: 184) error code = 1, system error = 0, msg1 = (null), msg2 = (null), msg3 = (null), msg4 = (null)
Solution:
For S_APP_QUERY table it runs the following command:
update S_APP_QUERY
set OWNER_ID = CREATED_BY
where OWNER_ID is NULL
In SEA 7.7 the S_APP_QUERY_U1 index is unique and contains the columns (name, desc_text, created_by, lang_id, conflict_id)
In SEA 8.1.1 the S_APP_QUERY_U1 is unique and contains the columns (name, desc_text, owner_id , lang_id, conflict_id)
Since the indexes are recreated after the preschm.sql execution, and owner_id is a new column added containing NULLS, the column OWNER_ID would be updated with the values of column CREATED_BY, used in the 7.7 SEA index before the U1 index recreation.
For this reason, the data duplication faced by your upgrep execution was not caused by the upgrade itself, but something environment specific.
If the upgrade execution that failed with duplicate rows error was the first execution, the S_APP_QUERY table version 7.7 had a kind of damage, such as U1 not implemented accordingly, etc.
Notice please that customers should not manually change the db without the Technical Support analysis and recommendation, since this is not supported.
There is also another requirement for the connect string which Cfg Server Manager creates.
It requires that the Language and Locale code setting for the invoking object manager be set the same as for the eProdCfgMgr component (ENU for example in this case). From reviewing the customer's siebns.dat file it was found that in this case the customer
had theirs set to ZAR.
Once this was set to ENU and the server restarted, the connection to remote eConfigurator was successful.
There was also a question in relation to the Cfg Server Manager component as to whether this is an actual server component visible from the Administration - Server Management views. The answer is as follows:
Cfg Server Manager is not a real Object Manager(OM) but rather a piece of code residing in each OM and responsible for selecting the right eProdCfg OM. For the path it is using the Locale
parameter instead of Language.
"Understanding Dedicated Product Configurator Server Functionality Using Distributed Cache â Version 7.5.3.x and 7.7.x (Note 478069.1)" article gives further
details on this component.