I am facing Database timed-out issue while creating a view and/or rebasing a stream on vobs
ERROR -> cleartool: Error: Database timed out -- aborting transaction: "\TP".
ERROR -> cleartool: Error: Unable to generate config spec for stream "stream name".
I am using CCRC to connect.
CCRC possibly means CC8.0.X+, but you would still need to access logs (that was cleartool getlog in previous CC versions, since you mentioned before using CC 7.1), in order to know more about that error message.
A "Database timed out -- aborting transaction" usually is followed on the logs by the actual root cause (like, for instance, db_VISTA database error -926 - problem in shared memory lock manager)
In the OP's case, it was (from this technote), a corrupt transaction file.
Error: db_VISTA error -925
Database timed out error is resolved after following this http://www-01.ibm.com/support/docview.wss?uid=swg21133944
Lock the VOB (if you receive errors from the lock command, proceed to step 2.)
Unmount the VOB
Kill any lingering VOB processes on the server using the albd_list utility.
Note: Review technote 1148639 for more details on albd_list and its usage.
Should some ClearCase processes still exist that are accessing the transaction files and preventing you from deleting them, you must completely - stop ClearCase on the server to end those processes.
Move the vista.tjf, vista.tcf, vista.taf files out of the VOB db directory
Refer to technote 1149322 About ClearCase database vista.* files for further information about these files.
Remount the VOB
The files will be recreated and the VOB will be functional
Note: If the files are not recreated, stop and restart ClearCase services on the host.
Related
I'm getting [INS-35180] Unable to check for available memory error while installing Oracle 19c in my laptop. I have tried to run DBCA as admin but still facing the same issue.
Error: [INS-35180] Unable to check for available memory.
Details: Additional Information:
Exception details - PRVG-1901 : failed to setup CVU remote execution framework directory "C:\Users\u720770\AppData\Local\Temp\InstallActions2023-02-08_06-14-10PM\CVU_19.0.0.0.0_u720770" on nodes "blrl52gm6g3"
Please select a different work area for the framework
blrl52gm6g3 : PRKN-1014 : Failed to execute remote command "C:\Users\u720770\AppData\Local\Temp\InstallActions2023-02-08_06-14-10PM\CVU_19.0.0.0.0_u720770\exectask.exe" on node "BLRL52GM6G3".Failed during connecting to service
blrl52gm6g3 : Failed during connecting to service
Version of exectask could not be retrieved from node "blrl52gm6g3"
I did below steps.
Downloaded Oracle 19c from Oracle site.
Extracted the zip file and copied it to C: drive.
Renamed the folder to 'db_home'
Ran setup file as administrator.
Please let me know how to resolve this issue to be able to install Oracle 19c.
Hello Can you check this path really exists and permissions on exectask.exe allow you to execute ?
C:\Users\u720770\AppData\Local\Temp\InstallActions2023-02-08_06-14-10PM\CVU_19.0.0.0.0_u720770\exectask.exe
or maybe it could be this bug
Bug 28747089 - DBCA Errors Out During Verification-- Unable to check for available memory (Doc ID 28747089.8) To BottomTo Bottom
or this
After applying Microsoft KB, DBCA Fails With [DBT-50000] Unable To Check For Available Memory (Doc ID 2807229.1)
SOLUTION
Make a note of the directory from which the OracleRemoteExecService is running; usually it is %temp% or c:\windows\temp. This information is available in the Service Control Manager.
Delete the OracleRemExecService.
Clean all the files under the directory from which OracleRemoteExecService was running, i.e. %temp% or c:\windows\temp.
It looks like I dont have enough admin privileges. I was able to install successfully after obtaining admin privileges.
I am trying to export a dump file and log file on a remote machine using oracle expdp.
However i am getting the following error :
Connected to: Oracle Database 11g
Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing
options
ORA-39002: invalid operation
ORA-39070: Unable to open the log file.
ORA-29283: invalid file operation
ORA-06512: at "SYS.UTL_FILE", line 536
ORA-29283: invalid file operation
Command run on remote machine host-name 'Local' using oracle client are :
SQL> create directory expdp_dir as '/vault2/expdp_dir';
SQL> grant read,write on directory expdp_dir to dbuser;
expdp dbuser/dbpwd#SID SCHEMAS=dbuser DIRECTORY=expdp_dir DUMPFILE=testDB24NOV17.dmp logfile=testDB24NOV17.log EXCLUDE=STATISTICS
Note vault 2 is mounted on a remote machine with hostname 'Local'. The database is on a machine with hostname TestDB.
The OS is RHEL6.
Any thoughts /ideas on making this operation successful would be appreciated.
Please check this one:
as per Oracle Doc.ID Doc ID 1305166.1
The errors can have multiple causes. Known causes are listed below.
One of the usual reasons for this problem to occur is when the listener process has not been started under the same account as the database instance service. The listener forks the new server process and when this runs under a different security context as the database, then access to directories and files are likely impacted.
Please verify the following information:
1) the output of:
ps -ef | grep SMON
2) the output of:
ps -ef | grep tnslsnr
3) the output of:
ps -ef|grep LIST
4) the output of:
ls -ld
Note:
When using ASM, the listener may have been started from the ASM Home instead of the RDBMS Home. Depending on your security settings, this may give to this issue.
One more:
4. Directory path/folder exists but create directory is executed by a different user in the database and the import is run by a different user.
Solution:
1. Make sure the listener and instance services are started from the same account.
Make sure that the directory are shared between nodes so that the directory can be accessed on any instance, or, create a folder similar to the other nodes locally, if there is already a folder created locally on the all the node with the same file directory path structure check if the permission are correct.
Make sure the folder exist has specified in during creation in the "CREATE DIRECTORY" syntax command.
Grant the required permission to the importing user to use the directory.
grant read, write on directory to ;
If above 4 possible causes and solutions are not applicable at your end, please check if the user has proper permission to export to run utl_file package.
Hope it helps.
I am trying to build a standby database in a Data Guard configuration using RMAN Duplicate Target Database For Standby Dorecover.
All the rman backupsets are there in Netbackup and I can see the inventory of backup pieces using the RMAN views.
However, the Duplicate Target Database command is failing with:
channel p4: starting datafile backup set restore
channel p4: restoring control file
channel p4: reading from backup piece c-2404308342-20160306-02
channel p4: ORA-19870: error while restoring backup piece c-2404308342-20160306-02
ORA-19507: failed to retrieve sequential file, handle="c-2404308342-20160306-02", parms=""
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text:
Backup file <c-2404308342-20160306-02> not found in NetBackup catalog
Basically, the backup pieces are there, but RMAN/Netbackup is saying that they are not there.
Do you know why?
Thank you.
Please try validating the restore with a validate restore command. It should take some time but will notify you of any backup corruptions.
e.g. RMAN > restore database validate;
Thanks
Sabiha
Oracle version 11.2.0.3.
I restored a dev DB from Prod, then i got the following error after partially restored the DB. I cannot open the DB even in mount.
ORA-01103: database name 'PROD_DB' in control file is not 'DEV_DB'
The restore errors are listed below, I thought I can try to open the DB, but failed from the above error.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/15/2015 15:43:14
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of archived log for thread 1 with sequence 171836 and starting SCN of 6104951872 found to restore
RMAN-06025: no backup of archived log for thread 1 with sequence 171835 and starting SCN of 6104939057 found to restore
How can i fix it?
After reading some online posts from this website regarding the same error, but the answers were all wrong. Here is how it worked.
I cannot save the control file to trace becuase i cannot open the DB in mount.
I cannot change the DB name with the same reason: cannot mount the DB
So i focused on the RMAN error and went to the Prod db and added a few more archive log backuks to ensure that all logs are saved on the backup device, NetBackup
I then changed the restore time about 20 minutes earlier to ensure i have archive logs there.
It worked like a charm.
Thanks
I have a stream ClearCase (UCM) stream. The snapshot view update started failing with error.
cleartool: Error: Unable to access "C:\views\qe-lis_2014.1\ctools_src\src\chsboot\test\exe\jcechecksumtest.exe.loading": Permission denied.
cleartool: Error: Unable to transfer a file: Permission denied.
cleartool: Error: Unable to copy "c\cdft\b\1f\65a681eb2ed247f7850957f17516b8cd" to "C:\views\qe-lis_2014.1\ctools_src\src\chsboot\test\exe\jcechecksumtest.exe.loading": Permission denied.
cleartool: Error: Unable to load "jcechecksumtest.exe".
A dynamic view on same stream on same machine works fine. A snapshot view created from another machine works fine too. How can I find more information on this and fix the error?
Versions
machine with error: ClearCase 7.1.1.4 (Windows NT 6.1 (build 7601) Service Pack 1 Pentium)
machine working fine: ClearCase 7.1.1.3 (Windows NT 6.1 (build 7601) Service Pack 1 Pentium)
Edit #1
I do not have admin rights
One way to troubleshoot is to ask the ClearCase admin to go to the vob server, in c\cdft\b\1f\ and check if the permissions are somehow different from the other elements.
As mentioned in this old thread:
There are a bunch of steps for cleaning permissions (e.g. protectvob, cleartool protect) that should always be run you restore from backup.
Fundamentally, you want to check the vob permissions on the physical repository and the permissions as you see them from within a view.
Also check your view storage - even better create new views.
On the client side, you can check if the issue persists with:
other snapshot views on your computer
other snapshot views (on the same UCM stream) for other users (on other computers)
make sure your CLEARCASE_PRIMARY_GROUP environment variable is still set to the primary group of the Vob you want to access.
Since another view on another machine works, you can compare their properties by doing:
cd /path/to/snapshot:view
cleartool lsview -l -full -pro -cview