My Oracle Support Banner

Siebel Upgphys "Merge And Conflict Resolution Complete" Step Fails With "No Rows Fetched" error in verify_irm.log Post Incremental Repository Merge (IRM) Step (Doc ID 2707278.1)

Last updated on JUNE 05, 2023

Applies to:

Siebel CRM - Version 8.1.1.9 [23016] and later
Information in this document applies to any platform.

Symptoms

When attempting to run upgphys after IRM, upgphys step fails during the first step and following errors are seen in upgwiz.log.

UpgradeLog UpgradeInfo 3 000000025f4e0530:0 2020-09-01 10:56:23 Executing (cmd /c find "rows fetched:" "C:\Siebel\ses\siebsrvr\log\upgphys_dev_82214\output\verify_irm.log")
UpgradeLog UpgradeError 1 000000025f4e0530:0 2020-09-01 10:56:23 (err=1) was returned by application (cmd /c find "rows fetched:" "C:\Siebel\ses\siebsrvr\log\upgphys_dev_82214\output/verify_irm.log").
UpgradeLog UpgradeError 1 000000025f4e0530:0 2020-09-01 10:56:23 File to execute (cmd) does not exist.

verify_irm.log fails shows below error which indicates the actual problem.

Database Version
ODBC driver: dbspecific.dll version xxxx
(login time:)
SELECT ACTIVITY_NAME FROM S_INST_UPG_HIST WHERE ACTIVITY_NAME='Incremental Repository Merge'
(query+fetch time: 0.05s, no rows fetched)
ODBCSQL: Exit at timestamp (status 0)


STEPS TO REPRO
-------------------
The issue can be reproduced at will with the following steps:

1. Perform upgrade to any version from 8.1.1.9 that involves IRM
2. Make sure upgrep and IRM is executed
3. Execute upgphys and check to see if it is completed

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.