It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×1,192

question asked: Mar 10 '11, 3:45 p.m.
question was seen: 3,797 times
last updated: Mar 10 '11, 3:45 p.m.

Related questions

Clean up build step log entries before upgrading to 7.1.2.1

0
Sonica Lieou-Jackson (15●1●4●5) | asked Mar 10 '11, 3:45 p.m.
We're testing the upgrade of RBF/RAFW 7.1.2.1. RBF is installed on Solaris 10 and we are running Oracle 10.2.0.4.

We found out through the upgrade process and through support that in the 7.1.2.1 the BF_LOGS table (which stores the build log steps) gets converted to CLOB from 7.1.1.3. There is a process that runs to do this conversion and it can take days if your BF_LOGS tables contains millions of rows.

Our thought is to reduce these millions of rows before we actually upgrade the production environment so that the conversion process doesn't take forever. Has anyone seen this and what have you done to reduce the entries in the BF_LOGS table before the upgrade?

Thanks in advance!
sljhhsc

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
David Brauneis (506●1●1) | answered Apr 05 '11, 10:24 p.m.
JAZZ DEVELOPER
We're testing the upgrade of RBF/RAFW 7.1.2.1. RBF is installed on Solaris 10 and we are running Oracle 10.2.0.4.

We found out through the upgrade process and through support that in the 7.1.2.1 the BF_LOGS table (which stores the build log steps) gets converted to CLOB from 7.1.1.3. There is a process that runs to do this conversion and it can take days if your BF_LOGS tables contains millions of rows.

Our thought is to reduce these millions of rows before we actually upgrade the production environment so that the conversion process doesn't take forever. Has anyone seen this and what have you done to reduce the entries in the BF_LOGS table before the upgrade?

Thanks in advance!
sljhhsc


I would suggest that you that a look at the results that you have stored and consider purging some of the results if they are no longer needed.
0
permanent link
Sonica Lieou-Jackson (15●1●4●5) | answered Apr 06 '11, 9:50 a.m.
We're testing the upgrade of RBF/RAFW 7.1.2.1. RBF is installed on Solaris 10 and we are running Oracle 10.2.0.4.

We found out through the upgrade process and through support that in the 7.1.2.1 the BF_LOGS table (which stores the build log steps) gets converted to CLOB from 7.1.1.3. There is a process that runs to do this conversion and it can take days if your BF_LOGS tables contains millions of rows.

Our thought is to reduce these millions of rows before we actually upgrade the production environment so that the conversion process doesn't take forever. Has anyone seen this and what have you done to reduce the entries in the BF_LOGS table before the upgrade?

Thanks in advance!
sljhhsc


I would suggest that you that a look at the results that you have stored and consider purging some of the results if they are no longer needed.


Thank you for the suggestions. This is exactly what we did. We also worked with support to located (via SQL script) and remove the really large records.

Thanks,
sljhhsc

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.