Siebel System Admin, Install and Upgrade (MOSC)

MOSC Banner

25.6 Patch ODBC Migration Bug - ODBC hardcoded to default value and not customer's actual value

in Siebel System Admin, Install and Upgrade (MOSC) 4 commentsAnswered

Hi All,

Making some progress getting closer to getting 25.6 patch to work. Found what has to be a new bug. When the patch tries to migrated the existing ODBC data sources to the new driver for the Server ODBC it is using the default ODBC name derived from the default enterprise name ES1.

I had to create this ODBC get rid of the error I was seeing. For my install out enterprise is called SIA and our server ODBC is SIA_DSN and not ES1_DSN. The server log files show the proof.

2025-07-03T13:51:46.779507400Z main WARN No Root logger was configured, creating default ERROR-level Root logger with Console appender

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

SBL Sys Admin Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center