Applies to:
Siebel Tools - Version: 7.0.4.11 [14073] to 8.0.0.5 [20420] - Release: V7 to V8Information in this document applies to any platform.
Symptoms
Customer was running a batch job to deactivate workflows with following SQL:
SELECT
T1.CONFLICT_ID,
T1.LAST_UPD,
T1.CREATED,
T1.LAST_UPD_BY,
T1.CREATED_BY,
T1.MODIFICATION_NUM,
T1.ROW_ID,
T1.DESCRIPTION,
T1.NAME
FROM
SIEBEL.CX_INT_PARAM T1
WHERE
(T1.TYPE = 'PARAMETER') AND
(T1.PAR_ROW_ID = '1-2IKG')
This generates the following error in the EAIObjMgr log:
SBL-DBC-00104: Error retrieving next record from the database.
SQLParseAndExecute Execute 5 0 2009-05-12 17:34:09 ORA-24345: A Truncation or null fetch error occurred
ObjMgrSqlCursorLog Close 5 0 2009-05-12 17:34:09 Begin: Close Sql Cursor at 869b820
ObjMgrSqlCursorLog Trace 5 0 2009-05-12 17:34:09 SQL Cursor with ID 869B820 Fetch Rows: 20, Fetch All
Time: 0.003 seconds.
ObjMgrBusCompLog Error 1 0 2009-05-12 17:34:09 (buscomp.cpp (16578)) SBL-DBC-00104: Error retrieving next record from the database.
Running the SQL directly on the database returns 85 rows with no problems.
Customer increased the buffer size on the database and restarted the server it but we still experience the same problem.
Cause
This problem occured as a result of a physical db schema change.Solution
This schema change altered the DESCRIPTION column from VARCHAR(255) to VARCHAR(500)
This extra length on the column was causing an "buffer overflow" issue when an attempt was made to map the values to the logical siebel schema.
Applies to:
Siebel Tools - Version: 7.0.4.11 [14073] to 8.0.0.5 [20420] - Release: V7 to V8Information in this document applies to any platform.
Symptoms
Customer was running a batch job to deactivate workflows with following SQL:
SELECT
T1.CONFLICT_ID,
T1.LAST_UPD,
T1.CREATED,
T1.LAST_UPD_BY,
T1.CREATED_BY,
T1.MODIFICATION_NUM,
T1.ROW_ID,
T1.DESCRIPTION,
T1.NAME
FROM
SIEBEL.CX_INT_PARAM T1
WHERE
(T1.TYPE = 'PARAMETER') AND
(T1.PAR_ROW_ID = '1-2IKG')
This generates the following error in the EAIObjMgr log:
SBL-DBC-00104: Error retrieving next record from the database.
SQLParseAndExecute Execute 5 0 2009-05-12 17:34:09 ORA-24345: A Truncation or null fetch error occurred
ObjMgrSqlCursorLog Close 5 0 2009-05-12 17:34:09 Begin: Close Sql Cursor at 869b820
ObjMgrSqlCursorLog Trace 5 0 2009-05-12 17:34:09 SQL Cursor with ID 869B820 Fetch Rows: 20, Fetch All
Time: 0.003 seconds.
ObjMgrBusCompLog Error 1 0 2009-05-12 17:34:09 (buscomp.cpp (16578)) SBL-DBC-00104: Error retrieving next record from the database.
Running the SQL directly on the database returns 85 rows with no problems.
Customer increased the buffer size on the database and restarted the server it but we still experience the same problem.
Cause
This problem occured as a result of a physical db schema change.Solution
This schema change altered the DESCRIPTION column from VARCHAR(255) to VARCHAR(500)
This extra length on the column was causing an "buffer overflow" issue when an attempt was made to map the values to the logical siebel schema.
Applies to:
Siebel Tools - Version: 7.0.4.11 [14073] to 8.0.0.5 [20420] - Release: V7 to V8Information in this document applies to any platform.
Symptoms
Customer was running a batch job to deactivate workflows with following SQL:
SELECT
T1.CONFLICT_ID,
T1.LAST_UPD,
T1.CREATED,
T1.LAST_UPD_BY,
T1.CREATED_BY,
T1.MODIFICATION_NUM,
T1.ROW_ID,
T1.DESCRIPTION,
T1.NAME
FROM
SIEBEL.CX_INT_PARAM T1
WHERE
(T1.TYPE = 'PARAMETER') AND
(T1.PAR_ROW_ID = '1-2IKG')
This generates the following error in the EAIObjMgr log:
SBL-DBC-00104: Error retrieving next record from the database.
SQLParseAndExecute Execute 5 0 2009-05-12 17:34:09 ORA-24345: A Truncation or null fetch error occurred
ObjMgrSqlCursorLog Close 5 0 2009-05-12 17:34:09 Begin: Close Sql Cursor at 869b820
ObjMgrSqlCursorLog Trace 5 0 2009-05-12 17:34:09 SQL Cursor with ID 869B820 Fetch Rows: 20, Fetch All
Time: 0.003 seconds.
ObjMgrBusCompLog Error 1 0 2009-05-12 17:34:09 (buscomp.cpp (16578)) SBL-DBC-00104: Error retrieving next record from the database.
Running the SQL directly on the database returns 85 rows with no problems.
Customer increased the buffer size on the database and restarted the server it but we still experience the same problem.
Cause
This problem occured as a result of a physical db schema change.Solution
This schema change altered the DESCRIPTION column from VARCHAR(255) to VARCHAR(500)
This extra length on the column was causing an "buffer overflow" issue when an attempt was made to map the values to the logical siebel schema.
Applies to:
Siebel Tools - Version: 7.0.4.11 [14073] to 8.0.0.5 [20420] - Release: V7 to V8Information in this document applies to any platform.
Symptoms
Customer was running a batch job to deactivate workflows with following SQL:
SELECT
T1.CONFLICT_ID,
T1.LAST_UPD,
T1.CREATED,
T1.LAST_UPD_BY,
T1.CREATED_BY,
T1.MODIFICATION_NUM,
T1.ROW_ID,
T1.DESCRIPTION,
T1.NAME
FROM
SIEBEL.CX_INT_PARAM T1
WHERE
(T1.TYPE = 'PARAMETER') AND
(T1.PAR_ROW_ID = '1-2IKG')
This generates the following error in the EAIObjMgr log:
SBL-DBC-00104: Error retrieving next record from the database.
SQLParseAndExecute Execute 5 0 2009-05-12 17:34:09 ORA-24345: A Truncation or null fetch error occurred
ObjMgrSqlCursorLog Close 5 0 2009-05-12 17:34:09 Begin: Close Sql Cursor at 869b820
ObjMgrSqlCursorLog Trace 5 0 2009-05-12 17:34:09 SQL Cursor with ID 869B820 Fetch Rows: 20, Fetch All
Time: 0.003 seconds.
ObjMgrBusCompLog Error 1 0 2009-05-12 17:34:09 (buscomp.cpp (16578)) SBL-DBC-00104: Error retrieving next record from the database.
Running the SQL directly on the database returns 85 rows with no problems.
Customer increased the buffer size on the database and restarted the server it but we still experience the same problem.
Cause
This problem occured as a result of a physical db schema change.Solution
This schema change altered the DESCRIPTION column from VARCHAR(255) to VARCHAR(500)
This extra length on the column was causing an "buffer overflow" issue when an attempt was made to map the values to the logical siebel schema.
Applies to:
Siebel Tools - Version: 7.0.4.11 [14073] to 8.0.0.5 [20420] - Release: V7 to V8Information in this document applies to any platform.
Symptoms
Customer was running a batch job to deactivate workflows with following SQL:
SELECT
T1.CONFLICT_ID,
T1.LAST_UPD,
T1.CREATED,
T1.LAST_UPD_BY,
T1.CREATED_BY,
T1.MODIFICATION_NUM,
T1.ROW_ID,
T1.DESCRIPTION,
T1.NAME
FROM
SIEBEL.CX_INT_PARAM T1
WHERE
(T1.TYPE = 'PARAMETER') AND
(T1.PAR_ROW_ID = '1-2IKG')
This generates the following error in the EAIObjMgr log:
SBL-DBC-00104: Error retrieving next record from the database.
SQLParseAndExecute Execute 5 0 2009-05-12 17:34:09 ORA-24345: A Truncation or null fetch error occurred
ObjMgrSqlCursorLog Close 5 0 2009-05-12 17:34:09 Begin: Close Sql Cursor at 869b820
ObjMgrSqlCursorLog Trace 5 0 2009-05-12 17:34:09 SQL Cursor with ID 869B820 Fetch Rows: 20, Fetch All
Time: 0.003 seconds.
ObjMgrBusCompLog Error 1 0 2009-05-12 17:34:09 (buscomp.cpp (16578)) SBL-DBC-00104: Error retrieving next record from the database.
Running the SQL directly on the database returns 85 rows with no problems.
Customer increased the buffer size on the database and restarted the server it but we still experience the same problem.
Cause
This problem occured as a result of a physical db schema change.Solution
This schema change altered the DESCRIPTION column from VARCHAR(255) to VARCHAR(500)
This extra length on the column was causing an "buffer overflow" issue when an attempt was made to map the values to the logical siebel schema.
No comments:
Post a Comment