# psrinfo -p 2 # psrinfo -pv The physical processor has 64 virtual processors (0-63) UltraSPARC-T2+ (cpuid 0 clock 1165 MHz) The physical processor has 64 virtual processors (64-127) UltraSPARC-T2+ (cpuid 64 clock 1165 MHz) # psrinfo -v | more Status of virtual processor 0 as of: 08/12/2009 12:01:00 on-line since 08/08/2009 06:03:02. The sparcv9 processor operates at 1165 MHz, and has a sparcv9 floating point processor. Status of virtual processor 1 as of: 08/12/2009 12:01:00 on-line since 08/08/2009 06:03:05. The sparcv9 processor operates at 1165 MHz, and has a sparcv9 floating point processor. Status of virtual processor 2 as of: 08/12/2009 12:01:00 on-line since 08/08/2009 06:03:05. The sparcv9 processor operates at 1165 MHz, and has a sparcv9 floating point processor. ......... Finding cores To find total number of cores across all the CPUs : # kstat cpu_info|grep core_id|sort -u|wc -l 16 Now to find number of core per CPU simply do the math : total number of cores / total number of physical CPUs Another way of gathering CPU related info is using the prtdiag command : # prtdiag -v | more System Configuration: Oracle Corporation sun4v SPARC T2+ Memory size: 65536 Megabytes ================================ Virtual CPUs ================================ CPU ID Frequency Implementation Status ------ --------- ---------------------- ------- 0 1400 MHz SPARC-T2+ on-line 1 1400 MHz SPARC-T2+ on-line 2 1400 MHz SPARC-T2+ on-line 3 1400 MHz SPARC-T2+ on-line 4 1400 MHz SPARC-T2+ on-line 5 1400 MHz SPARC-T2+ on-line 6 1400 MHz SPARC-T2+ on-line 7 1400 MHz SPARC-T2+ on-line 8 1400 MHz SPARC-T2+ on-line 9 1400 MHz SPARC-T2+ on-line 10 1400 MHz SPARC-T2+ on-line 11 1400 MHz SPARC-T2+ on-line 12 1400 MHz SPARC-T2+ on-line 13 1400 MHz SPARC-T2+ on-line 14 1400 MHz SPARC-T2+ on-line 15 1400 MHz SPARC-T2+ on-line .... Gathering Memory information Getting memory information is trivial. use the prtconf command and grem for Memory : # prtconf | grep Memory Memory size: 65536 Megabytes We can also use the prtdiag command to find the memory in the system : # prtdiag -v | grep Memory Memory size: 65536 Megabytes Finding CPU information on T-series hardware with LDOMs If you have LDOMs installed on the T-series hardware tyhat you have, above commands may not give you the correct values. Use the “ldm list-devices -a” command to list core, virtual CPUs (VCPUs) and resource assignments. # ldm list-devices -a CORE ID %FREE CPUSET 0 12 (0, 1, 2, 3, 4, 5, 6, 7) 1 0 (8, 9, 10, 11, 12, 13, 14, 15) 2 0 (16, 17, 18, 19, 20, 21, 22, 23) 3 0 (24, 25, 26, 27, 28, 29, 30, 31) 4 0 (32, 33, 34, 35, 36, 37, 38, 39) 5 0 (40, 41, 42, 43, 44, 45, 46, 47) 6 0 (48, 49, 50, 51, 52, 53, 54, 55) 7 0 (56, 57, 58, 59, 60, 61, 62, 63) 8 0 (64, 65, 66, 67, 68, 69, 70, 71) 9 0 (72, 73, 74, 75, 76, 77, 78, 79) 10 0 (80, 81, 82, 83, 84, 85, 86, 87) 11 0 (88, 89, 90, 91, 92, 93, 94, 95) 12 0 (96, 97, 98, 99, 100, 101, 102, 103) 13 0 (104, 105, 106, 107, 108, 109, 110, 111) 14 0 (112, 113, 114, 115, 116, 117, 118, 119) 15 0 (120, 121, 122, 123, 124, 125, 126, 127) 16 0 (128, 129, 130, 131, 132, 133, 134, 135) ........................... Number of physical cpu: psrinfo -p Number of cores: kstat cpu_info|grep core_id|sort -u|wc -l Number of threads: psrinfo -pv # echo "`psrinfo -p` socket(s)" 2 socket(s) # echo "`kstat -m cpu_info|grep -w core_id|uniq|wc -l` core(s) " 8 core(s) # echo "`psrinfo|wc -l` logical (virtual) processor(s)" 64 logical (virtual) processor(s)
Posts Tagged ‘syed ali immam rizvi’
Sun Solairs Server Commands
November 3rd, 2026, posted in SolarisRMAN-06059: Expected Archived Log Not Found, Loss Of Archived Log Compromises Recoverability
October 5th, 2026, posted in Oracle QueriesError :
RMAN> BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG;
Starting backup at 18-NOV-21
current log archived
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 11/18/2021 17:29:50
RMAN-06059: expected archived log not found, loss of archived log compromises recoverability
ORA-19625: error identifying file /u02/immam/db/apps_st/data/archive/1_500_1195296918.dbf
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Solution :
Once in a while, there will be an archive log that is expired but not deleted.
If that is the case, there is an easy answer :
RMAN> crosscheck archivelog all;
RMAN> list expired archivelog all;
RMAN> delete expired archivelog all;Now, run the backup again.. It will work !!
Views We Qery In Database
September 7th, 2026, posted in Oracle Queries1} V$CONTROLFILELists the names and status of the control files.
2} V$DATABASEContains database information from the control files.
3} V$DATAFILEContains data file information from control file.
4} V$INSTANCEDisplays the state of the current instance.
5} V$PARAMETERLists parameters and values currently in effect for the Session also status and location of all parameters.
6} V$SESSIONLists session information for each current session.
7} V$SGAContains summary information on SGA.
8} V$SPPARAMETERLists the contents of SPFILE.
9} V$TABLESPACEDisplays tablespace information from the control file.
10} V$THREADContains thread information from control file.
11} V$VERSIONVersion numbers of core library components in oracle server.
12} V$FIXED_TABLETo find list of data dictionary views.
13} V$CONTROLFILE_RECORD_SECTIONProvides information about the Control file record section.
14}SHOW PARAMETER CONTROL_FILESLists the name, status and location of Control files.
15}V$THREADTo display the current redo log group, the no. of online redo log groups and current sequence number.
16} V$LOGFILEDisplays each redo log group, member and status of each Member.
17} V$LOG Same as above.
18} V$DATABASE_PROPERTIESName of default tablespaces.
19}V$DBA_TABLESPACESComplete information about tablespaces.
20}V$DBA_DATA_FILESComplete information of the files present in the Tablespaces.
21} V$DBA_TEMP_FILESFile’s information of temporary tablespace.
22} V$DBA_EXTENTSTo check the extents for a given segment.
23} V$DBA_SEGMENTSView to get number of extents and blocks allocated to a Segment.
24} V$DBA_FREE_SPACEDisplays free extents in tablespace.
25} V$DBA_ROLLBACK_SEGSTo obtain information about all the undo segments In the database. {IMP*:-Information about undo segments that are offline can be seen only in this view.}
26}V$ROLLSTAT & V$ROLLNAMEViews to obtain the statistics of the undo Segments currently used by the instance.
27} V$TRANSACTION & V$SESSIONTo check the use of a undo segment by Currently active transactions.
28} V$DBA_TABLESAll the information about tables can be obtained here.
29} V$DBA_OBJECTSAll the information about objects in table can be obtained here.
30} V$DBA_UNUSED_COL_TABSTo identify tables with unused columns.
31} V$DBA_PARTIAL_DROP_TABSTo identify tables that have partially Completed DROP columns operations.
32}V$DBA_INDEXESProvides information on the indexes.
33}V$DBA_IND_COLUMNSProvides information on the columns indexed.
34}V$OBJECT _USAGEProvides information on the usage of an index.
35}V$DBA_CONSTRAINTSTo obtain name, type and status of all constraints.
36}V$DBA_CONS_COLUMNSTo obtain the columns in the constraints on table.
37}V$DBA_USERSTo obtain information about account status, default Tablespace for users.
38}V$DBA_PROPERTIES View to display passwd profile information.
39}V$DBA_TS_QUOTAS Amount of space a user can use in tablespaces.
40}V$DBA_SYS_PRIVS Lists system privileges granted to users and roles.
41} V$SESSION_PRIVS Lists the privileges that are currently available to user.
42} V$DBA_TAB_PRIVSLists all grants on all objects in the database.
43}V$DBA_COL_PRIVS Describes all object grants in the database.
44}V$DBA_ROLESAll roles that exist in the database.
45}V$DBA_ROLES_PRIVSRoles granted to users and roles.
46}V$ROLE_ROL_PRIVSRoles that are granted to roles.
47}V$DBA_SYS_PRIVS System privileges granted to users and roles.
48}V$ROLE_SYS_PRIVSSystem privileges granted to roles.
49}V$ROLE_TAB_PRIVSObject privileges granted to roles.
50}V$SESSION_ROLESRoles that the user currently has enabled
Obsolete Backups Vs RMAN Expired
August 30th, 2026, posted in Oracle EBS Application, Oracle QueriesObsolete Backups Vs RMAN Expired
Understand and manage expired and obsolete backups in RMAN.
Two terms that are very important when it comes to RMAN backups validation they are
- Expired Backups
- Obsolete Backups
Expired backups
Let’s take you trigger an RMAN backup and someone deleted backup set or backup pieces at OS level. The database CONTROFILE has the details of the backup on disk but at OS level the backup file does not exists.
We can run RMAN crosscheck command to check if backup files exists at OS level or not. If the backup files are not found, RMAN will mark it as EXPIRED.
RMAN> crosscheck backup;
DBA Action
The first action a DBA must take is to find out where the backup pieces are. Did a junior DBA move them to different location or different disk due to space issues.
If you can find the backup pieces, put them back into the original location and run crosscheck backup command again via RMAN.
If you are not able to find backup pieces, then you must clear the expired backup entries from RMAN (controlfile). Use below command to delete expired backups
RMAN> delete expired backup;
Obsolete backups
The general meaning of OBSOLETE is no longer used or required.
RMAN considers backups as OBSOLETE when they are no longer required for database recovery. This is done by one of the RMAN CONFIGURATION parameters.
For example, we set RMAN retention policy to redundancy 4. This means that if we have 5 database backups, the first one will be marked as OBSOLETE because we want to keep 4 copies of RMAN backups.
We use below command to list all the obsolete backups inside RMAN
RMAN> report obsolete;
DBA Action
IF the FRA location is full, then do not worry, RMAN is intelligent, it will overwrite the obsolete backups.
If you find obsolete backups, you can simply delete the backups (as they are no longer needed for recovery)
RMAN> delete obsolete;
