Announcement

Collapse
No announcement yet.

Risk with Custom Table?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Risk with Custom Table?

    Dear Pals,

    In OTM DB, by the time of Patch Update / Version upgrade, we will loose custom tables. Is this true?

    If the answer is yes,
    1) In what case of above two scenario's we will loose custom tables?
    2) what is prevention for this? Do we need to create a separate table space? If yes what is the procedure to create a table space?

    Cheers,
    Lakshman
    Cheers,
    Murthy

  • #2
    Re: Risk with Custom Table?

    Lakshman,

    Creating new objects within the OTM schema is not recommended.

    Alternately, you can create the custom objects and schema under a separate DB user, so that you don't have to worry about having them deleted, modified, or interfering with the OTM patch and migration process.

    --Chris

    Comment


    • #3
      Re: Risk with Custom Table?

      Thanks Chris.

      Could you pls explain me the procedure of creating our own schema and and providing the right grants to "glogowner", so that we can access the custom Db from OTM front end as and when it is required.

      Thanks & Regards,
      Lakshman
      Cheers,
      Murthy

      Comment


      • #4
        Re: Risk with Custom Table?

        Lakshman,

        Please excuse the brief reply - I'm preparing to travel and am running short on time today

        Creating the user and schema don't require any OTM-specific skills - so your Oracle DBA should be able to handle without an issue. As for table grants, here's a good link to give you an overview on the process:

        Oracle/PLSQL: Grant/Revoke Privileges

        --Chris

        Comment


        • #5
          Re: Risk with Custom Table?

          Thanks for the reply Chris. I will check with DBA.

          Regards,
          Lakshman
          Cheers,
          Murthy

          Comment

          Working...
          X