Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

REDO LOG and ARCHIVE LOG size

user13026028Apr 22 2010 — edited Apr 22 2010
Please take this as very theoretical question, there is no actual server in place yet ...

I have mid-size solaris 10 server with Oracle 10.2, the main tablespace (or better say few tablespaces) will have 3TB. This will be data warehouse server (smaller instance with maybe 20-30 users), and daily loads which will not exceed 50GB (50gb is really overstated number). There will be archive log with daily backups.

1. What is the rule of thumb as a decent size initial REDO and ARCHIVE LOG size? I know there is no way to give me exact number, I am talking high level ballpark here.


2. We will have 6 SAN filesystems attached to the server, would you recommend to use one for data, one for archive log and 2 for redo or would you rather use all 6 evenly for all data files (redo, archive, data, index, temp, ...).

Comments

Timo Hahn

User, tell us your jdev version, please!

Well, it's one way to do it (and not too bad). However, it always depends on hte use case. The method used in the blog allows you to navigate back and forth and holds all rows in memory. If you only want to visit each row, but don't plan to navigate (other than forward), you can use an optimized VO where you set the navigation in the VO to 'forward only'. Then for larger row sets page ranging is a better alternative as only one page of rows are read into memory.

Timo

Vladimir Zhilyaev

Hi, Timo.

Thanks for reply.

My jdev is 11.1.1.7.

My use case is "copy" view object data to other adf table. Which approach should I use?

This is my not working code:

  public void copyPayrolls1(ActionEvent actionEvent){

        DCIteratorBinding prlInfoIter = ADFUtils.findIterator("PayrollInfoIterator");

        DCIteratorBinding prlVOIter = ADFUtils.findIterator("PayrollVO1Iterator");

      

        RowSetIterator prlInfoRowSet = prlInfoIter.getRowSetIterator();

      

        ViewObject vo = prlVOIter.getViewObject();

        vo.executeQuery();

        while (vo.getRowSet().hasNext()) {

            Row newRow = prlInfoRowSet.createRow();

          

            newRow.setAttribute("payrollName",vo.getCurrentRow().getAttribute("PayrollName"));

            newRow.setAttribute("legalName",vo.getCurrentRow().getAttribute("LegalName"));

            newRow.setAttribute("payrollID",vo.getCurrentRow().getAttribute("PayrollId"));

            prlInfoRowSet.insertRow(newRow);

            System.out.println("asd");

        }

        prlInfoRowSet.closeRowSetIterator();

    }

Thanks

Timo Hahn

You can do it the way you coded it, if the number of rows to copy is small. For bigger row sets I would use a special VO whihc uses range paging amd only forward navigation.

Timo

1 - 3
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on May 20 2010
Added on Apr 22 2010
2 comments
1,543 views