I'm on a system with several LPARS. Each LPAR calls its own database XYZ. In the RDB directory, each LPAR refers to the the databases on the other LPARS by their LPAR name, but refers to itself as XYZ. This means that no matter where SQL runs, CURRENT_SERVER is always XYZ. This is annoying when one is trying to determine which environment something is running in.
Can anyone think of any drawbacks to changing this. We have no applications that check CURRENT_SERVER presently, and it would be pointless if they did.
And assuming we do want to change this, how do we do it?
Pinned topic Multiple LPARS using same RDB name
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-04-04T13:59:59Z at 2013-04-04T13:59:59Z by krmilligan
krmilligan 120000MDWP450 Posts
Re: Multiple LPARS using same RDB name2013-04-04T13:59:59ZThis is the accepted answer. This is the accepted answer.Shouldn't be any issues in changing it - assuming you don't have active host server jobs (eg, ODBC & JDBC requests) that are connected to that database.
WRKRDBDIRE command would allow you to change the name of the *LOCAL entry.