Read Only Database?

Sort:
You are not authorized to post a reply.
Author
Messages
David Schronce
Basic Member
Posts: 5
Basic Member

    Working with S3 on Oracle DB in Unix.  We want to make a copy of the productline and data as of midnight 1/1/22 for archival reporting.  That much is no problem but it means setting the DB readonly so NOBODY can fool with the data - BUT...  we want to be able to report against that data.  Of  course jobs can't be created/saved on a locked DB ,so I'm thinking about moving the LA system code to a different DB instance that is unlocked.

    The last time I did this the database was all in LADB.

    Anyone know if this is still feasible - and HOPEFULLY have a doc on making it happen?

    Thanks!

    Kwane McNeal
    Veteran Member
    Posts: 479
    Veteran Member
      This is pretty much what you have to do.

      With Oracle you can just setup different tablespaces, but the goal is the same.

      Also you may want to do this at the table level (CKPOINT), versus whole system code, because depending on the jobs, you may need more than CKPOINT to be writable.

      And of course, you’re aware that a number of tables in GEN needs to be writable
      You are not authorized to post a reply.