Tags » Database

Maintenance tasks associated with the evolution of a database.

As the database evolves we may have to support the following:

  • Multi-user access to the same records.
  • Concurrent access to the database,
  • Increased number of transactions.
  • 11 more words
Degree

Different start options in Oracle databases

STARTUP NOMOUNT:
————————————-
STARTUP NOMOUNT starts the instance without mounting the database. When a database is started in this mode, the parameter file is read and the background processes and memory structures are initiated, but they are not attached or communicating with the disk structures of the database. 488 more words

Oracle Databases

Turning off Recycle bin in Oracle Database

Login to your database

Before making the below change , Please check the content and size of dba_recyclebin
Check the current values of recyclebin parameter. 90 more words

Oracle Databases

Setting Up Huge Pages in Exadata

Below are the steps taken to configure huge pages on each exadata node.

1)  Ensure that all  DB instances are up an running on the node. 464 more words

Oracle Databases

Dropping Restore Point in Read Only Physical Standby Databases

While dropping restore point on standby databases i got below error.

SYS@NFTBINT1>drop restore point GRPT_BF_UPGR1;
drop restore point GRPT_BF_UPGR1
*
ERROR at line 1:
ORA-16000: database open for read-only access… 259 more words

Oracle Databases

Oracle Database 12C Charset Change from US7ASCII to WE8MSWIN1252.

We are going to migrate our database charset from US7ASCII to WE8MSWIN1252.

In our Scenario the new character set is a strict superset of the current character set, so it is possible to use the ALTER DATABASE CHARACTER SET to expedite the change in the database character set. 234 more words

Oracle 12c

PG::Error: ERROR: column reference “created_at” is ambiguous

In rails convention we have every table having columns like created_at , updated_at and id . Now check what happens in the below example.

I have a table named users from which I am accessing statuses, both have column names created_at , now postgres is confused depending on which created_at the statuses must be ordered, and which created_at must be involved in comparison statement. 38 more words