Categories
Databases

RCU:6107 DB Init Param error

While Installing Repository Creation Utility (RCU) Installation the following error occurs:

RCU:6107 DB Init Param Error

This can be removed simply by the following:

1. Login on your database with system user.

2. Write > show parameters processes (which will show the current value of processes).

3. If its value is less than 500 then write the following command:

ALTER SYSTEM SET PROCESSES=500 SCOPE=SPFILE;

4. Write > show parameters open_cursors (which will show the current value of open_cursors).

5. If its value is less than 500 then write the following command:

ALTER SYSTEM SET OPEN_CURSORS=500 SCOPE=SPFILE;

6. Restart your DB or system.

7. Start the installation now….

Categories
Databases

Oracle 11G: Starting the DB, listener and the enterprise manager console

Make sure all the necessary environment variables are set, especially the following variables.

  1. ORACLE_SID
  2. ORACLE_HOME
And follow the below steps to start, database, listener and enterprise manager(em) console
  • For db startup: 

             [email protected]sqlplus / as sysdba
SQL*Plus: Release 11.1.0.6.0 – Production on Sun Nov 9 22:52:26 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to an idle instance.

SQL> startup;
ORACLE instance started.
Total System Global Area 1389391872 bytes
Fixed Size 1299848 bytes
Variable Size 838863480 bytes
Database Buffers 536870912 bytes
Redo Buffers 12357632 bytes
Database mounted.
Database opened.

SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 – Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

  • Starting listener
              [email protected]$ lsnrctl start
  • Oracle Enterprise manager start
              [email protected]$  emctl start dbconsole
Now the enterprise manager server is started and can be accessed using the link on browser : https://hostname:1158/em
Thank u 🙂
Categories
Databases

Mysql common questions and answers

CREATE USER

CREATE USER ‘jeffrey’@’localhost’ IDENTIFIED BY ‘mypass’;

Create user without password.

CREATE USER ‘jeffrey’@’localhost’;

DROP User

DROP USER ‘jeffrey’@’localhost’;

GRANT

Steps:

CREATE USER ‘jeffrey’@’localhost’ IDENTIFIED BY ‘mypass’;

GRANT ALL ON db1.* TO ‘jeffrey’@’localhost’;

GRANT SELECT ON db2.invoice TO ‘jeffrey’@’localhost’;

GRANT USAGE ON *.* TO ‘jeffrey’@’localhost’ WITH MAX_QUERIES_PER_HOUR 90;

RENAME USER

RENAME USER ‘jeffrey’@’localhost’ TO ‘jeff’@’127.0.0.1’;

SET PASSWORD

SET PASSWORD FOR ‘bob’@’%.loc.gov’ = PASSWORD(‘newpass‘);

Or

UPDATE mysql.user SET Password=PASSWORD(‘newpass‘)

WHERE User=’bob’ AND Host=’%.loc.gov’;

FLUSH PRIVILEGES;

Or

GRANT USAGE ON *.* TO ‘bob’@’%.loc.gov’ IDENTIFIED BY ‘newpass‘;

MYSQLDUMP BACKUP

Syntax:

shell> mysqldump [options] db_name [tbl_name ...]

shell> mysqldump [options] --databases db_name ...

shell> mysqldump [options] --all-databases

examples:

mysqldump -u root -p[root_password] [database_name] > dumpfilename.sql

MYSQLDUMP RESTORE

Syntax:

mysql db_name < script.sql > output.tab

Examples:

mysql -u root -p[root_password] [database_name] < dumpfilename.sql

RECOVER/RESET mysql root password.

·Stop mysql service

#/etc/init.d/mysql stop

·Start mysql server w/o password

#mysqld_safe –skip-grant-tables &

·Connect to mysql server using mysql client

# mysql -u root

·Setup new password for mysql root user

mysql> use mysql; mysql> update user set password=PASSWORD(“NEW-ROOT-PASSWORD”) where User=’root’; mysql> flush privileges; mysql> quit

·Stop mysql server.

/etc/init.d/mysql stop

·Start server in normal mode & test

# /etc/init.d/mysql start # mysql -u root -p