ORA-00845: MEMORY_TARGET not supported on this system

June 9, 2014 Leave a comment

Today, I tuned the memory_target to 8G on a 11g instance, it showed the errors above when it got restarted. It was caused by the tmpfs size.

[oracle@yhktamvmdb01 etc]$ df -h
Filesystem            Size  Used Avail Use% Mounted on
tmpfs                 7.8G  164K  7.8G   1% /dev/shm <– the size less than 8G.
/dev/sda1             485M   37M  423M   9% /boot

Then, I increased the size by the command below

[root@yhktamvmdb01 ~]# mount -t tmpfs shmfs -o size=12g /dev/shm

[root@yhktamvmdb01 ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
tmpfs                  12G     0   12G   0% /dev/shm <– the size increased to 12G

Start the database successfully

SQL> startup
ORACLE instance started.

Total System Global Area 8551575552 bytes
Fixed Size                  2270360 bytes
Variable Size            5049944936 bytes
Database Buffers         3489660928 bytes
Redo Buffers                9699328 bytes
Database mounted.
Database opened.

Make the change on the tmpfs permanently by editing the /etc/fstab as the following

tmpfs                   /dev/shm                tmpfs   size=12g        0 0

 

 

 

 

Categories: ORA-XXX

Enable VNC Server on Solaris 10

May 21, 2014 Leave a comment

1. Add entry below intop /etc/services

vnc-server      5900/tcp                        # Xvnc

2. Create /etc/X11/gdm/custom.conf with entries below

xdmcp]
Enable=true
[security]
DisallowTCP=false
AllowRoot=true
AllowRemoteRoot=true

3. Enable the svc

# svcadm enable svc:/application/x11/xvnc-inetd:default
# svcs  xvnc-inetd
STATE          STIME    FMRI
online         14:41:27 svc:/application/x11/xvnc-inetd:default

 

Categories: Solaris Admin

ORA-28040: No matching authentication protocol

April 17, 2014 Leave a comment

I just install 12C1 database. When the old client 8 connected to the database, it showed the error below.

ORA-28040: No matching authentication protocol

Fixed:

Add the parameter below into $ORACLE_HOME/network/admin/sqlnet.ora. This set SQL

SQLNET.ALLOWED_LOGON_VERSION=8

 

Categories: Uncategorized

mysql_secure_installation showed ERROR 2002 (HY000): Can’t connect to local MySQL server through socket ‘/tmp/mysql.sock’ (2)

April 4, 2014 Leave a comment

Today, I secured the mysql db with the mysql_secure_installation. It showed the following errors.

root@slave1 mysql]# ./bin/mysql_secure_installation

NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MySQL
SERVERS IN PRODUCTION USE!  PLEASE READ EACH STEP CAREFULLY!

In order to log into MySQL to secure it, we’ll need the current
password for the root user.  If you’ve just installed MySQL, and
you haven’t set the root password yet, the password will be blank,
so you should just press enter here.

Enter current password for root (enter for none):
ERROR 2002 (HY000): Can’t connect to local MySQL server through socket ‘/tmp/mysql.sock’ (2)
Enter current password for root (enter for none):
ERROR 2002 (HY000): Can’t connect to local MySQL server through socket ‘/tmp/mysql.sock’ (2)
Enter current password for root (enter for none):

Caused:

Since I have set the mysqld socket to /opt/mysql/run/mysqld.sock in /etc/my.cnf as the following, not the default path /tmp/mysql.sock.

[mysqld]
# basic setting
datadir = /opt/mysql/data
tmpdir = /opt/mysql/tmp
socket = /opt/mysql/run/mysqld.sock

Fixed:

I added one more line “/opt/mysql/run/mysqld.sock” into /usr/local/mysql/bin/mysql_secure_installation at make_config section as the following. Then the problem got fixed.

sub make_config {
my $password = shift;

my $esc_pass = basic_single_escape($rootpass);
write_file($config,
“# mysql_secure_installation config file”,
“[mysql]“,
“user=root”,
“password=’$esc_pass'”,
“connect-expired-password”,
“socket=/opt/mysql/run/mysqld.sock”);
}

 

 

Categories: mySQL troubleshooting

tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x4)

March 13, 2014 Leave a comment

On the standby dataguard  10.2.3 db, the  xxxxx_mrp0_xxx.trc showed the messages when executing “alter system archive log crrent”

MRP: Prodding archiver at standby for thread 1 seq 45077
tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x4)
tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x4)
MRP: Prodding archiver at standby for thread 2 seq 31006
tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x4)
tkcrrpa: (WARN) Failed initial attempt to send ARCH message (message:0x4)

According to oracle support, it is a bug.( LGWR unconditionally writes to trace file ). The workaround solution is to set log_archive_max_proesses to high count. ( I set it to 10). The warning disappeared after the change.

Categories: Oracle Bug

ORA-00031: session marked for kill

January 28, 2014 Leave a comment

1. Kill a session, returned the message below.

SQL>  alter system kill session ‘1022,851’;
alter system kill session ‘1022,851’
*
ERROR at line 1:
ORA-00031: session marked for kill

2. Find out the OS process id

SQL> select a.spid,b.sid,b.serial#,b.username from v$process a,v$session b where a.addr=b.paddr and b.status=’KILLED';

SPID         SID           SERIAL# USERNAME
———— ———- ———- ——————————
15198        ##########        851 EHEALTH

3. Go to OS to find the server process

[oracle@yplodb02 ~]$ ps -ef|grep 15198
oracle   15198     1  1 Jan20 ?        03:41:07 oracleehealthp1 (LOCAL=NO)

oracle    9140 13829  0 15:38 pts/4    00:00:00 grep 15198

4. Kill it by OS command

[oracle@yplodb02 ~]$ kill -9 15198

[oracle@yplodb02 ~]$ ps -ef|grep 15198
oracle   12522 13829  0 15:38 pts/4    00:00:00 grep 15198

 

 

 

 

Categories: Administration, ORA-XXX

Purge dba_scheduler_job_log

January 28, 2014 Leave a comment

 

SQL> exec DBMS_SCHEDULER.PURGE_LOG();

Categories: Administration
Follow

Get every new post delivered to your Inbox.