nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

OBIEE 12c RPD Corrupted

Rajesh Dhanapal

Hi,

OBIEE version : 12.2.1.4.0

During the Prodcution freeze period, downloaded the RPD from the prod environment and made the some changes and uploaded the RPD in non-prod environment for some testing. Although prod RPD was untouched in the prod environment, suddenly all the OBIEE generated SQL's in the live environment was not qualified with schema name prefix and hence all users reports were failing with table or view does not exisit. In-order to resolve the issue I have again uploaded the same PROD RPD(without any modifications) in to production environment and SQL's started generating with schema name prefix.

I have checked the log files when the issue occured other than table or view does not exist there is no any other errors. I would like to know the root cause behind this issue, so we can avoid any future occurances.

NB: I have double checked PROD environment and RPD timestamp was old when the issue occured and RPD was not touched at all during the prod freeze and not opened in online mode too.

Best regards,

Rajesh Dhanapal.

Find more posts tagged with

Accepted answers

All comments

Joel Acha

How do you download/upload your rpd?
Which changes did you make in the non Prod rpd?
Which log files have you looked at and were there any errors?
Is this 12.2.1.4?
Which OS?

As you can see, there are a lot of questions that need to be answered first.

Gianni Ceresa

2668432 wrote:RPD was not touched at all during the prod freeze and not opened in online mode too.

6. How do you know nobody/nothing touched the RPD on your PROD environment?

Rajesh Dhanapal

1. Using the scripts

../Oracle_Home/user_projects/domains/bi/bitools/bin/data-model-cmd.sh downloadrpd -O liverpd_`date '+%d-%m-%Y'`.rpd -SI ssi -U weblogic

../Oracle_Home/user_projects/domains/bi/bitools/bin/data-model-cmd.sh uploadrpd -I liverpd_`date '+%d-%m-%Y'`.rpd -SI ssi -U weblogic

2. Permission changes for Subject Area

3. PS, BI server, Admin server, basically I looked into all the logs

4. Yes the versions is 12.2.1.4

5. Red hat linux.

Apolgies for not adding these information on the initial request.

Rajesh Dhanapal

Hi Gianni,

I checked the timestamp to ensure nothing has changed when the issue started occuring in the prod. To be very precise the issue started in the PROD at 8:47am on 27th Dec and I have downloaded the RPD around that sort of time. I checked the timestamp of the PROD rpd and it was haivng the older timstamp and hence nothing is touched/changed in the PROD envrionment.

Best regards,

Rajesh Dhanapal.

[Deleted User]

2668432 wrote:Hi Gianni,I checked the timestamp to ensure nothing has changed when the issue started occuring in the prod.

And what "timestamp" would that be? Of your own command line output? That proves nothing as nobody is required to add that - it's not a real source control but just some bits sthat get added to a file name.

Also: You are aware that an RPD can be modified in online mod I hope. You can only ever be really sure of what happened if you look at the delta XML which gets stored on the server itself.

Rajesh Dhanapal

Hi Christian,

Timestamp in the PROD version after the issue occured was from the last release. In the command lineout I have added manually for just our internal reference.

Also as mentioned in my original request, RPD was not modified in online mode.

When you say delta XML - Is it this location you are referring to - ../Oracle_Home/user_projects/domains/bi/bidata/service_instances/ssi/metadata/datamodel/customizations. Which has got rpdVariables_diff.xml, connectionPools_diff.xml, metadataUpdateDefault_diff.xml? If yes, all these files are not impacted on issue date

[Deleted User]

Yes. Those files. They contain what really happened to the RPD.

Our point is: Changes can't appear magically. Somebody or something has to have modified the metadata. Either a human being or a process.