Author: dbalifeeasy

How to Check if Remote Network Port Open or Not Without Telnet on Windows

Use TNC in powershell

C:\>powershell
...
..
.
PS C:\> tnc google.com -port 80


ComputerName     : google.com
RemoteAddress    : 172.217.167.110
RemotePort       : 80
SourceAddress    : 10.11.12.13
TcpTestSucceeded : True


PS C:\> tnc google.com -port 99
WARNING: TCP connect to (142.250.204.14 : 99) failed


ComputerName           : google.com
RemoteAddress          : 142.250.204.14
RemotePort             : 99
SourceAddress          : 10.11.12.13
PingSucceeded          : True

TcpTestSucceeded       : False

ORA-15041: diskgroup “FRA” space exhausted

The following errors occur in Oracle database alert log :

...
..
.
Unable to create archive log file '+FRA'
Errors in file /u01/app/oracle/diag/rdbms/testdb/TESTDB1/trace/TESTDB1_arc1_12300.trc:
ORA-19816: WARNING: Files may exist in db_recovery_file_dest that are not known to database.
ORA-17502: ksfdcre:4 Failed to create file +FRA
ORA-15041: diskgroup "FRA" space exhausted

CAUSE

Diskgroup FRA had been overallocated, the sum of db_recovery_file_dest_size of all the databases is more than the size of diskgroup FRA.

SQL> select NAME,TOTAL_MB,FREE_MB from v$asm_diskgroup
;

NAME                             TOTAL_MB    FREE_MB
------------------------------ ---------- ----------
...
..
.
FRA                               1024142       120

RESOLUTION

Decrease ‘db_recovery_file_dest_size” for some or all databases, and make sure the diskgroup FRA is not overallocated.

ORA-03206: maximum file size of (4194304) blocks in AUTOEXTEND clause is out of range (DBD ERROR: OCIStmtExecute) from Corrective Action of Add Space to Tablespace

OEM add space to tablespace corrective action failed with the following ORA-03206 error:

...
..
.
OMF directory: +DATAC1
OMF disk group: DATAC1
ASM projected safely usable free space (MB) is: 28548641.667
ASM projected Space Used (%) is: 59.11
Add datafile SQL is: ALTER TABLESPACE "TEST" ADD DATAFILE SIZE 7291M AUTOEXTEND ON NEXT 100M MAXSIZE 32768M
Execute(ALTER TABLESPACE "TEST" ADD DATAFILE SIZE 7291M AUTOEXTEND ON NEXT 100M MAXSIZE 32768M) failed:ORA-03206: maximum file size of (4194304) blocks in AUTOEXTEND clause is out of range (DBD ERROR: OCIStmtExecute)
Disconnected from database

CAUSE

For small datafile tablespace, the maximum datafile size is 32GB ( 32768M ) in theory. But in actual situation, the given size should be little less than 32GB.

SOLUTION

Explicitly specify the maximum datafile size to 31GB ( 31744 M ), for example, instead of the default 32GB ( 32768M ) in corrective action parameters configuration.

Before

Maximum Datafile Size (GB)

After

Maximum Datafile Size (GB)31
...
..
.
OMF directory: +DATAC1
OMF disk group: DATAC1
ASM projected safely usable free space (MB) is:  28548641.667
ASM projected Space Used (%) is: 59.11
Add datafile SQL is: ALTER TABLESPACE "TEST" ADD DATAFILE SIZE 7291M AUTOEXTEND ON NEXT 100M MAXSIZE 31744M
Successfully added new datafile

ORA-39142: incompatible version number 4.2 in dump file

The following errors occur when running impdp on same database version 12.1.0.2 as the source database:

ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-39142: incompatible version number 4.2 in dump file "/tmp/exp_tables.dmp"

SOLUTION

  • Apply patches to the same patch level for both source and target database.

OR

  • Use parameter VERSION.
$ expdp  ... VERSION=12.1 ...