Clone from hot backup failing with ORA-19870, 19505 unable to find backup

Ok, the steps I am taking worked previously, the only thing that I know changed was the underlying file system and I am perplexed but then again I am not the most experienced dba so please forgive if I miss something obvious.
My steps are: create backup using:
backup database tag= tagname format '/archive/stage/DBNAME/%U';
backup archivelog all format '/archive/stage/DBNAME/%U';
backup current controlfile '/archive/stage/DBNAME/%U';
Then on the new server, I copy the files over to the new server and:
connect target username@prod
connect auxillary
set until time
duplicate target database to "PRODSBX"
etc...
The problem is the duplicate is not looking at my '/archive/stage/DBNAME' directory for the backup. It's looking in the normal backup directory on that prod box that it can't connect to... can anyone give me clues as to what I should be looking at to figure out why? I looked at file permissions in case it couldn't access this directory, I looked at id, group etc... and I am not seeing anything. These exact same scripts worked before... the only thing I have edited is the set until time so I just can't figure out why it's not going to the /archive/stage.
Any light shed in my general direction would be greatly appreciated.
Thanks!
Va.

I have no way to copy the output of the files as this is on a closed network. If there is any particular information you are looking for I'd be happy to post it.
The restore is looking for the default backup location as specified in my rman configuration but in my backup script, I specify a different location that I do the hot backup to. The first time it took this location and successfully cloned to the new server and now it seems to be ignoring it. I am not sure why, any suggestions in what I should look at, if this is a possible configuration issue on my clone server or on my primary?
Thanks,
Va.

Similar Messages

RMAN backup failes with ORA-19624 occurred during call to DBMS_BACKUP_RESTO

RMAN backup up failes with following errors. It works some times and then failes. When it failes then if i un install and reinstall Oralec agent and Backup cliet then it start working OK for few days and then again start getting error. See the messages below...
Recovery Manager: Release 8.1.7.0.0 - Production
RMAN-06005: connected to target database: MIMSDEVH (DBID=3525230908)
RMAN-06008: connected to recovery catalog database
RMAN> RUN { 2> execute script tapelevel0; 3> }
RMAN-03021: executing script: tapelevel0
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03015: error occurred in stored script tapelevel0
RMAN-03007: retryable error occurred during execution of command: allocate
RMAN-07004: unhandled exception during command execution on channel ch00
RMAN-10035: exception raised in RPC: ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-19557: device error, device type: SBT_TAPE, device name:
ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer
ORA-19511: SBT error = 4110, errno = 0, BACKUP_DIR environment variable is not set
RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.DEVICEALLOCATE
Send me some solution...

hi,
what is your backup script
can you post back the result of the command
show all;
from the rman command prompt
regards
Alan

Export backup failing with ORA-1555snapshot too old: rollback segment ERROR

DB version =8.1.7.4
OS=Solaris =5.10.
I know this is outdated. But still we are supporting this version of database.
We are facing ORA-1555 error daily when we are running the export backup of database. Consistent parameter is set to N .
I needed to know why export uses rollback segments during export operation. even though CONSISTENT parameter is N.
Thanks,
Edited by: ahshivap on Dec 12, 2012 5:19 AM

Hi,
Consistent=y just mean the tables are consistent with each other. Oracle still has to guarantee that each individual table is at least consistent with itself. That's your issue.
Regards,
Harry

Archived log application to a cold backup fails with ora-00328

I am testing backup and recovery scenario as mentioned in Metalink Doc id:69468.1 where a cold backup of one production server is restored on a separate machine. Some activity, say a table creation in some schema and insertion of rows in it is followed by a few log switches. Next I moved just the archived logs ( newly generated) to the test machine and proceed as follow to recover but log application is failing as below,any help would be appreciated!
SQL> startup mount;
ORACLE instance started.
Total System Global Area 205520896 bytes
Fixed Size 1248116 bytes
Variable Size 71304332 bytes
Database Buffers 130023424 bytes
Redo Buffers 2945024 bytes
Database mounted.
SQL> recover database until cancel using backup controlfile;
ORA-00279: change 581754 generated at 12/21/2007 02:35:04 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001
ORA-00280: change 581754 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00328: archived log ends at change 581535, need later change 581754
ORA-00334: archived log:
'C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001'
SQL> recover database until cancel;
ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
SQL> recover database until cancel using backup controlfile;
ORA-00279: change 581754 generated at 12/21/2007 02:35:04 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001
ORA-00280: change 581754 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
C:\oracle\product\10.2.0\archive\ARC00001_0641874107.001
ORA-00328: archived log ends at change 581535, need later change 581754
ORA-00334: archived log:
'C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001'
SQL> recover database using backup controlfile;
ORA-00279: change 581754 generated at 12/21/2007 02:35:04 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001
ORA-00280: change 581754 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
C:\oracle\product\10.2.0\archive\ARC00001_0641874107.001
ORA-00328: archived log ends at change 581541, need later change 581754
ORA-00334: archived log:
'C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001'
Please Help

The error displayed stated you are required to have an specific sequence:
ORA-00280: change 581754 for thread 1 is in sequence #1
Check the contents of the v$recover_file dynamic view and verify if you really have all required archivelog files.
~ Madrid

Time Machine fails with "error while linking files on the backup volume"

One of my drives was nearly full. I moved some folders from that drive to one that had more space.
The next TM backup failed with "error while linking files on the backup volume". A full backup is about 620 GB, although this backup shouldn't have been a complete one. There was 570+ GB free on the drive.
A Disk Verify reported "Drive appears to be okay." Earlier TM backups appeared to be fine (at least accessible). I swapped the TM drive for another, initialized it, and TM used that drive with no complaints.
What does the message mean?
Thanks,
harv47

Pondini wrote:
harv47 wrote:
The Time Machine Buddy widget shows no messages. None of the buttons do anything.
What am I doing wrong?
See #A1 in the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
Your user account may not have permission to see the logs.
The sentence beginning "If the message area is blank ..." shows how to figure out if that's the problem, and how to fix it.
Post back if it's not clear, or doesn't work.
The Tip had the answer. It was permissions.
What follow are the messages for the last unsuccessful TM backup (on v.3), followed by
the successful TM backup on the replacement drive (v.1). The line
"Copied 11 files (0 bytes) from volume Bay 3 HPFS+." was odd.
Starting standard backup
Backing up to: /Volumes/Time Machine v.3/Backups.backupdb
Event store UUIDs don't match for volume: Bay 3 HPFS+
Event store UUIDs don't match for volume: Macintosh HD
Node requires deep traversal:/Volumes/Bay 3 HPFS+ reason:kFSEDBEventFlagMustScanSubDirs|
Node requires deep traversal:/ reason:kFSEDBEventFlagMustSc
(Finished May 4, 2010 9:31:21 AM-- Status unknown)
Starting standard backup
Backing up to: /Volumes/TimeMachine v.1/Backups.backupdb
Event store UUIDs don't match for volume: Bay 3 HPFS+
Event store UUIDs don't match for volume: Bay 2 HPFS+
Event store UUIDs don't match for volume: Macintosh HD
Backup content size: 169.1 GB excluded items size: 0 bytes for volume Bay 3 HPFS+
Backup content size: 305.5 GB excluded items size: 0 bytes for volume Bay 2 HPFS+
Backup content size: 145.7 GB excluded items size: 7.5 MB for volume Macintosh HD
No pre-backup thinning needed: 744.36 GB requested (including padding), 931.15 GB available
Waiting for index to be ready (909 > 0)
Copied 1951 files (169.0 GB) from volume Bay 3 HPFS+.
Copied 4999 files (474.3 GB) from volume Bay 2 HPFS+.
Copied 410304 files (612.4 GB) from volume Macintosh HD.
No pre-backup thinning needed: 712.2 MB requested (including padding), 315.09 GB available
Copied 11 files (0 bytes) from volume Bay 3 HPFS+.
Copied 20 files (1.1 GB) from volume Bay 2 HPFS+.
Copied 1103 files (1.1 GB) from volume Macintosh HD.
Starting post-backup thinning
No post-back up thinning needed: no expired backups exist
Backup completed successfully.
(Finished May 4, 2010 2:38:17 PM)
I hope this is useful. Thanks for your help.
harv47

Adcfgclone fails with ORA-04063: view "SYS.DBA_NETWORK_ACLS" error

Hi all,
While running adcfgclone on dbtier if fails with following error
ORA-04063: view "SYS.DBA_NETWORK_ACLS" error
here is the scene:
we are trying to clone a production instance for doing some patching
while running adcfgclone on target (test instance) it fails
our current environment is
application:R12.1.3
db:11.1.0.7
os: rhel 5.6
here is output from
autoconfig file:
SQLPLUS Executable : /u02/testoba/db/tech_st/11.1.0/bin/sqlplus
SQL*Plus: Release 11.1.0.7.0 - Production on Thu Apr 18 09:28:32 2013
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Enter value for 1: Enter value for 2: Enter value for 3: Connected.
PL/SQL procedure successfully completed.
Commit complete.
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
adcrobj.sh exiting with status 0
ERRORCODE = 0 ERRORCODE_END
.end std out.
.end err out.
AutoConfig Services Phase
Running Service Process 2 of 4 for AppsUtil
Executing script in InstantiateFile:
/u02/testoba/db/tech_st/11.1.0/appsutil/install/TESTOBA_testsrv/addbperms.sh
script returned:
addbperms.sh started at Thu Apr 18 09:28:32 IST 2013
The environment settings are as follows ...
ORACLE_HOME : /u02/testoba/db/tech_st/11.1.0
ORACLE_SID : TESTOBA
TWO_TASK :
PATH : /u02/testoba/db/tech_st/11.1.0/perl/bin:/u02/testoba/db/tech_st/11.1.0/bin:/usr/bin:/usr/sbin:/u02/testoba/db/tech_st/11.1.0/appsutil/jre/bin:/bin:/usr/bin/X11:/usr/local/bin:/u02/testoba/db/tech_st/11.1.0/appsutil/clone/bin/../jre/bin:/u02/testoba/db/tech_st/11.1.0/appsutil/clone/bin/../jre/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/oratest/bin:.
Library Path : /u02/testoba/db/tech_st/11.1.0/lib:/usr/X11R6/lib:/usr/openwin/lib:/u02/testoba/db/tech_st/11.1.0/lib:/usr/dt/lib:/u02/testoba/db/tech_st/11.1.0/ctx/lib
SQLPLUS Executable : /u02/testoba/db/tech_st/11.1.0/bin/sqlplus
     Changing permissions for file sqlplus.
     Changing permissions for file extproc.
     Changing permissions for file tkprof.
addbperms.sh exiting with status 0
.end std out.
.end err out.
AutoConfig Services Phase
Running Service Process 3 of 4 for AppsUtil
Executing script in InstantiateFile:
/u02/testoba/db/tech_st/11.1.0/perl/bin/perl -I /u02/testoba/db/tech_st/11.1.0/perl/lib/5.8.3 -I /u02/testoba/db/tech_st/11.1.0/perl/lib/site_perl/5.8.3 -I /u02/testoba/db/tech_st/11.1.0/appsutil/perl /u02/testoba/db/tech_st/11.1.0/appsutil/install/TESTOBA_testsrv/txkConfigDbOcm.pl
script returned:
Configuring OCM on the Database Tier....
Testing database connection...
Database connection test passed.
Response file /u02/testoba/db/tech_st/11.1.0/appsutil/clone/adclnocm.res required to configure OCM does not exists
ERRORCODE = 0 ERRORCODE_END
.end std out.
.end err out.
AutoConfig Services Phase
Running Service Process 4 of 4 for AppsUtil
Executing script in InstantiateFile:
/u02/testoba/db/tech_st/11.1.0/appsutil/install/TESTOBA_testsrv/txkcreateACL.sh
script returned:
You are running txkcreateACL.sh version 120.1
The environment settings are as follows ...
ORACLE_HOME : /u02/testoba/db/tech_st/11.1.0
ORACLE_SID : TESTOBA
PATH : /u02/testoba/db/tech_st/11.1.0/perl/bin:/u02/testoba/db/tech_st/11.1.0/bin:/usr/bin:/usr/sbin:/u02/testoba/db/tech_st/11.1.0/appsutil/jre/bin:/bin:/usr/bin/X11:/usr/local/bin:/u02/testoba/db/tech_st/11.1.0/appsutil/clone/bin/../jre/bin:/u02/testoba/db/tech_st/11.1.0/appsutil/clone/bin/../jre/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/oratest/bin:.
Executable : /u02/testoba/db/tech_st/11.1.0/bin/sqlplus
Executing txkcreateACL.sql ...
SQL*Plus: Release 11.1.0.7.0 - Production on Thu Apr 18 09:28:33 2013
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected.
FROM DBA_NETWORK_ACLS
ERROR at line 17:
ORA-06550: line 17, column 8:
PL/SQL: ORA-04063: view "SYS.DBA_NETWORK_ACLS" has errors
ORA-06550: line 16, column 3:
PL/SQL: SQL Statement ignored
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
txkcreateACL.sh: exiting with status 1
.end std out.
.end err out.
[AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution. Errors are grouped by directory and phase.
The report format is:
<filename> <phase> <return code where appropriate>
[APPLY PHASE]
AutoConfig could not successfully execute the following scripts:
Directory: /u02/testoba/db/tech_st/11.1.0/appsutil/install/TESTOBA_testsrv
txkcreateACL.sh INSTE8_APPLY 1
AutoConfig is exiting with status 1
RC-50014: Fatal: Execution of AutoConfig was failed
Raised by oracle.apps.ad.clone.ApplyDatabase
StackTrace:
java.lang.Exception: RC-50014: Fatal: Execution of AutoConfig was failed
     at oracle.apps.ad.clone.ApplyDatabase.checkAutoConfigErr(ApplyDatabase.java:3192)
     at oracle.apps.ad.clone.ApplyDatabase.runCVMAndAutoConfig(ApplyDatabase.java:3010)
     at oracle.apps.ad.clone.ApplyDatabase.doConf(ApplyDatabase.java:649)
     at oracle.apps.ad.clone.ApplyDatabase.doApply(ApplyDatabase.java:473)
     at oracle.apps.ad.clone.ApplyDatabase.<init>(ApplyDatabase.java:366)
     at oracle.apps.ad.clone.ApplyDBTier.<init>(ApplyDBTier.java:110)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
     at java.lang.reflect.Constructor.newInstance(Unknown Source)
     at oracle.apps.ad.clone.util.CloneProcessor.run(CloneProcessor.java:67)
     at java.lang.Thread.run(Unknown Source)
please provide any suitable link or doc id or any workaround
thanks
Zavi

Hi;
Please review:
Adautocfg.Sh Fails With "ORA-01422: " While Executing Txkcreateacl.sh [ID 854746.1]
Database Cloning Failed With txkcreateACL.sh[36]: sqlplus [ID 603297.1]
R12 : Autoconfig script txkcreateACL.sh fails with error ORA-31003: Parent /sys/acls/ already contains child entry OracleEBS.xml [ID 1328458.1]
Regard
Helios

Backups fail with Insufficient privileges error

Oracle 9.2.0.5 database
Solaris Operating Sysstem
I needed to recreate one database recently from the backup. I used DUPLICATE TARGET DATABASE comamand to recreate database. And once client confirmed I removed old database and copied this new database to original location and recreated controlfile.
But the tape backups are failing ever since then.
Is it because of password file problems ? This is a a totally new database and also DBID is different . But database name is same and created from backups of old database.
Backups fail with this error.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-01031: insufficient privileges
But the RMANUSER has the same privileges as in other databases on this server.
SQL> select username,sysdba,sysoper from v$pwfile_users;
USERNAME SYSDB SYSOP
SYS TRUE TRUE
RMANUSER TRUE FALSE
SQL> select privilege from dba_sys_privs where grantee='RMANUSER';
PRIVILEGE
CREATE SESSION
UNLIMITED TABLESPACE
How to resolve this issue ?

I actually recreated the password file using orapwd utility. But when checked the V$PWFILE_USERS it showed no users. Not even SYS
And I tired to grant SYSDBA to RMANUSER. It failed with the following error.
ERROR at line 1:
ORA-01999: password file mode has changed from 'exclusive' to 'shared'
But the show parameter REMOTE showed that remote_login_passwordfile is still EXCLUSIVE. And database uses an INIT file, not SPFILE.
I had to move back the copy of Old password file and now it shows two users (SYS and RMANUSER) again.

Backups failing with error 19: the backup disk could not be resolved, or there was a problem mounting it

Hello all,
Doubt this issue relates to a recent and ugly issue but sharing anyways (resolved thanks to a user here: LaPastenague)
Time Capsule won't backup if Modem (Motorola SB6121) attached
This was on Feb 10th resolved. Few days later I upgraded to Yosemite. Backups were working fine since.
Yesterday I happen to notice my last backup was 5 days ago. I looked in the console logs and saw:
2/25/15 3:55:06.127 PM com.apple.backupd[2777]: Attempting to mount network destination URL: afp://Paul;AUTH=SRP@Time%20Capsule._afpovertcp._tcp.local./Data
2/25/15 3:55:17.778 PM com.apple.backupd[2777]: NAConnectToServerSync failed with error: 2 (No such file or directory) for url: afp://Paul;AUTH=SRP@Time%20Capsule._afpovertcp._tcp.local./Data
2/25/15 3:55:17.792 PM com.apple.backupd[2777]: Backup failed with error 19: The backup disk could not be resolved, or there was a problem mounting it.
2/25/15 3:57:18.808 PM com.apple.prefs.backup.remoteservice[2021]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
I called Apple. Their front line was clueless. He suggested resetting the TC (latest "tower" model btw") which then a backup kicked off YEAH
But the next hour it failed
Called Apple again, this time to Sr Advisor. He suggested factory reset of the TC and set up again. Also first backup worked then rest failed
Third call to Apple useless also. He was asking questions I didn't feel relevant. He also was asking me to reset the TC which I told him was done 2 hours prior. He asked me to reboot which I could NOT at that time.
I begged him to collect data to submit to engineering, which will take days to get a reply.
So I thought I would throw this out to the community....
TC Is NEW (replaced from last issue). Mac is 8 months old (iMac 27"), Os is Yosemite, TC also new (latest model)
Thanks...

Yosemite is problematic on two fronts.. Networking and Time Machine.. so the combo of doing both with a Time Capsule is like bugs on bugs.
Here is my standard list.. but your problem maybe difficult to resolve.. and my suggestion is simple.. until Apple get their act together and fix TM.. buy Carbon Copy Cloner and use that for your backup. It is solid and reliable.. even better if you use USB drive plugged into the computer and do a bootable clone.. because then you have a backup that is able to be tested for full functionality 2min after the end of the backup.
This also starts from a factory reset.. but the reason for it is to change the configuration which is much more easily handled with factory reset to begin.. the instructions are there.. because this is my standard reply.. this is not uncommon!!
Factory reset universal
Power off the TC.. ie pull the power cord or power off at the wall.. wait 10sec.. hold in the reset button.. be gentle.. power on again still holding in reset.. and keep holding it in for another 10sec. You may need some help as it is hard to both hold in reset and apply power. It will show success by rapidly blinking the front led. Release the reset.. and wait a couple of min for the TC to reset and come back with factory settings. If the front LED doesn’t blink rapidly you missed it and simply try again. The reset is fairly fragile in these.. press it so you feel it just click and no more.. I have seen people bend the lever or even break it. I use a toothpick as tool.
N.B. None of your files on the hard disk of the TC are deleted.. this simply clears out the router settings of the TC.
Setup the TC again.
ie Start from a factory reset. No files are lost on the hard disk doing this.
Then redo the setup from the computer with Yosemite.
1. Use very short names.. NOT APPLE RECOMMENDED names. No spaces and pure alphanumerics.
eg TCgen5 and TCwifi for basestation and wireless respectively.
Even better if the issue is more wireless use TC24ghz and TC5ghz with fixed channels as this also seems to help stop the nonsense. But this can be tried in the second round.
2. Use all passwords that also comply but can be a bit longer. ie 8-20 characters mixed case and numbers.. no non-alphanumerics.
3. Ensure the TC always takes the same IP address.. you will need to do this on the main router using dhcp reservation.. or a bit more complex setup using static IP in the TC. But this is important.. having IP drift all over the place when Yosemite cannot remember its own name for 5 min after a reboot makes for poor networking. If the TC is main router it will not be an issue.
4. Check your share name on the computer is not changing.. make sure it also complies with the above.. short no spaces and pure alphanumeric.. but this change will mess up your TM backup.. so be prepared to do a new full backup. Sorry.. keep this one for second round if you want to avoid a new backup.
5. Mount the TC disk in the computer manually.
In Finder, Go, Connect to server from the top menu,
Type in SMB://192.168.0.254 (or whatever the TC ip is which you have now made static. As a router by default it is 10.0.1.1 and I encourage people to stick with that unless you know what you are doing).
You can use name.. SMB://TCgen5.local where you replace TCgen5 with your TC name.. local is the default domain of the TC and doesn't change.
However names are not so easy as IP address.. nor as reliable. At least not in Yosemite they aren't. The domain can also be an issue if you are not plugged or wireless directly to the TC.
6. Make sure IPv6 is set to link-local only in the computer. For example wireless open the network preferences, wireless and advanced / TCP/IP.. and fix the IPv6. to link-local only.
There is a lot more jiggery pokery you can try but the above is a good start.. if you find it still unreliable.. don't be surprised.
You might need to do some more work on the Mac itself. eg Reset the PRAM.. has helped some people. Clean install of the OS is also helpful if you upgrade installed.
Tell us how you go.
Someone posted a solution.. See this thread.
Macbook can't find Time Capsule anymore
Start from the bottom and work up.. What I list here is good network practice changes but I have avoided Yosemites bug heaven.
This user has had success and a few others as well.
RáNdÓm GéÉzÁ
Yosemite has serious DNS bug in the networking application.. here is the lets say more arcane method of fixing it by doing a network transplant from mavericks.
http://arstechnica.com/apple/2015/01/why-dns-in-os-x-10-10-is-broken-and-what-yo u-can-do-to-fix-it/

All scheduled jobs started suddenly to fail with ORA-01031: insufficient pr

I have a setup of gridcontrol 11g on windows 2008. I've been running successful for weeks until the other day when all my scheduled jobs started to fail with
ORA-01031: insufficient privileges (rman jobs)
ERROR: Invalid username and/or password (sql scripts).
I verified for the accounts being locked, pw correct, expired / grace period, etc.
all good when I try from the command line. running an rman backup from the command line works great, but the same one through the job scheduler fails with ORA-01031.
I've dropped the jobs completely, recreated them again. same thing.
I'm using preferred credentials and dropped and recreated them. same thing.
I don't know where else to look. Only grid control scheduled jobs fail, but all of them do.
I'm using SQLNET.AUTHENTICATION_SERVICES= (NTS) in my sql.ne (always have).
we use a windows domain server / domain authentication for logging into boxes. I haven't changed any of my passwords.
I am probably looking in the wrong places. Anybody able to help?

Hi,
ERROR: Invalid username and/or password (sql scripts).This error message clearly tells that password is incorrect and "insufficient privileges" shows that perhaps you are using SYS user for running the jobs and password for user SYS is incorrect.
If you are specifying passwords in your scripts, i don't think you need to set preferred credentials.
Try following
1) Remove preferred credentials
2) Don't check password of user sys by locally logging in (because if Os authentication is on, even wrong password will allow you loging into the database and you will think that password is correct). Try connecting database using SYS user from a remote machine and check whether it accepts your password and make sure you have same password for your jobs and in sql scripts
3) If still problem, just for test, remove SQLNET.AUTHENTICATION_SERVICES= (NTS) and try
Salman

Backup fails with RMAN-08132

Hi
I'm trying to run rman backup on standby db. It seems like the backup completes but i'm getting the following message at the end. I cant issue commands like "list backup;" Fails with the same error. Tried searching metalink without any luck. Anyone seen this before??
Finished backup at 25-APR-07
RMAN-08132: WARNING: cannot update recovery area reclaimable file list
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of REFAF command on default channel at 04/25/2007 12:30:45
ORA-00604: error occurred at recursive SQL level 1
ORA-01219: database not open: queries allowed on fixed tables/views only
Any clues from you sharp-eyed dba's out there would be greatly appricated!!

There's an entry on metalink:
Known RMAN issues in Oracle10g
Doc ID: Note:363409.1
Inside this note search for 'WARNING: cannot update recovery area reclaimable file list'
Werner

Time Machine spends hours partially backing up and then fails with "Time Machine couldn't complete the backup due to a network problem." Tried suggestions I've seen on the forum.

Time Machine spends hours partially backing up and then fails with "Time Machine couldn't complete the backup due to a network problem." I've tried various suggestions I've seen on the forum but nothing has worked. TIme Machine worked fine for the last two years and just suddenly started having this problem every time. The only thing that was a little different is that the computer was off for a week while on vacation and then I added a large amount (20 GB) of photos. Now the requested backup size is 82GB, which is large, and process proceeds very slowly for 2-3 hours before failing with the message mentioned. I have more than enough available backup storage space for it. Before failing, Time Machine has backed up no more than 12GB or so of the backup. It fails during different files each time.
I've turned off the computer sleep feature, and I've checked that the NAS is set to never automatically power down. I normally backup over Wi-Fi, but I've also tried connecting to Ethernet and it still has the same problem. It's odd because I also have a MacBook Pro that is still backing up fine to the same NAS using the MacBook's Time Machine.
I am using an iMac with OS X 10.6.8 and an Iomega StorCenter ix2-200 NAS.
I have system logs that I can share if helpful. The logged messages vary a bit from run to run, but here are some messages that I've been seeing:
I always get this message near the beginning of the backup:
Event store UUIDs don't match for volume: Macintosh HD
I've gotten this messsage a number of times:
Bulk setting Spotlight attributes failed.
One Day
Stopping backupd to allow ejection of backup destination disk!
Another day
1/7/12 10:44:20 AM
mDNSResponder[18]
PenaltyTimeForServer: PenaltyTime negative -112916, (server penaltyTime -1132397006, timenow -1132284090) resetting the penalty
1/7/12 10:46:37 AM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x1106be94
1/7/12 10:46:37 AM
kernel
AFP_VFS afpfs_DoReconnect started /Volumes/TimeMachine prevTrigger 0 currTrigger 1
Another Day
1/6/12 8:03:22 AM
Google Chrome[164]
Cannot find function pointer CMPluginInFactory for factory 3487BB5A-3E66-11D5-A64E-003065B300BC in CFBundle/CFPlugIn 0x16f99e20 </Users/smarmer/Library/Contextual Menu Items/Google Notifier Quick Add CM Plugin.plugin> (not loaded)
1/6/12 8:04:02 AM
com.apple.backupd[193]
Copied 7.5 GB of 67.0 GB, 8866 of 8866 items
1/6/12 8:06:58 AM
/System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[1013]
No valid tickets, timing out
1/6/12 8:29:44 AM
mDNSResponder[19]
PenaltyTimeForServer: PenaltyTime negative -148702, (server penaltyTime 2056822773, timenow 2056971475) resetting the penalty
1/6/12 8:59:22 AM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa5ac380
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect started /Volumes/TimeMachine prevTrigger 0 currTrigger 1
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: soft mounted and hidden volume so do not notify KEA for /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
Another day
1/5/12 3:48:55 PM
mdworker[2128]
CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
1/5/12 4:24:54 PM
mDNSResponder[19]
PenaltyTimeForServer: PenaltyTime negative -42698, (server penaltyTime 1148718961, timenow 1148761659) resetting the penalty
1/5/12 4:29:58 PM
com.apple.backupd[2074]
Copied 586.4 MB of 67.0 GB, 9891 of 9891 items
1/5/12 4:39:00 PM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa1c0380

bokon0n wrote:
1/11/12 8:53:30 AM
com.apple.backupd[1169]
Warning: Destination /Volumes/TimeMachine does not support TM Lock Stealing
1/11/12 8:53:30 AM
com.apple.backupd[1169]
Warning: Destination /Volumes/TimeMachine does not support Server Reply Cache
Those indicate that your NAS is not fully compatible with Snow Leopard.
1/11/12 8:53:35 AM
kernel
jnl: disk2s2: replay_journal: from: 67182592 to: 78680064 (joffset 0xa7b8000)
1/11/12 8:53:39 AM
kernel
jnl: disk2s2: examining extra transactions starting @ 78680064 / 0x4b09000
1/11/12 8:53:39 AM
kernel
jnl: disk2s2: Extra txn replay stopped @ 79056896 / 0x4b65000
1/11/12 8:53:49 AM
kernel
jnl: disk2s2: journal replay done.
1/11/12 8:53:49 AM
fseventsd[41]
event logs in /Volumes/Time Machine/.fseventsd out of sync with volume. destroying old logs. (253512 14 253512)
1/11/12 8:53:50 AM
kernel
hfs: Removed 1 orphaned / unlinked files and 0 directories
That looks like a problem was found with the file system (data) on the TM disk. I don't know the details, but OSX tried to recover it from the journal, and found extra data on the drive. Likely a result of the incompatibility mentioned above.
1/11/12 9:47:40 AM
com.apple.backupd[1169]
Bulk setting Spotlight attributes failed.
That's a problem writing to the NAS drive.
But the backup continued after all this.
1/11/12 1:25:07 PM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x9d00b44
Something caused a disconnect. Can't tell from the log what it was.
I doubt it's a problem with something in OSX being damaged or corrupted, but reinstalling OSX isn't a major hassle, so might be worth a try.
To be incompatible with Snow Leopard, this NAS must be at least a couple of years old. It may be beginning to fail.
Contact the maker. See if there's an update to make it compatible with Snow Leopard. If so, that might fix it.
If not, or if that doesn't fix it, see if they have any diagnostics that will shed any light.

Windows 2008 R2 backup fails with event 521 error code 2155348001

Windows Server 2008 R2 SP1. Hyper-V role installed.
OS on drive C. All VMs stored on Drive D.
I am attempting to run a Bare Metal backup of the host system to a network share.
Drive D is not included in the backup job. I am getting the following error:
Log Name:      Application
Source:        Microsoft-Windows-Backup
Date:          1/10/2014 11:28:52 PM
Event ID:      521
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:      SHAQTUS.scdl.local
Description:
The backup operation that started at '‎2014‎-‎01‎-‎11T04:08:50.683000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348001'. Please review the event
details for a solution, and then rerun the backup operation once the issue is resolved.
Reviewing event details, as suggested, does not offer any solution.
I have tried the suggested solutions in other similar threads of increasing the timeout value with the registry entry.
This does not work.
I have not tried reregistering the VSS writers manually, as the only links I have found are for server 2003/2008 (not R2) and explicitly state that they won’t work on higher versions of the OS, since they now utilize manifests and the manual procedure could
cause problems for those servers. Haven't found similar procedures for 2008 R2.
I have been able to narrow this down a bit.
A Windows 2008 R2 SP1 server with Hyper-V installed – backup to a network share is successful;
Install the DPM 2012 agent – same backup fails with the 2155348001 error.
We use DPM 2012 to backup VMs, but DPM cannot perform a bare metal backup/restore of server and the 2012 version no longer has the DPMSRT feature.
I prefer to run Bare Metal Backup to a file server share.
Stuck on this one.
Rick

Hi,
The issue is related to DPM, I would suggest you ask for help from DPM forums:
http://social.technet.microsoft.com/Forums/en-US/home?forum=dataprotectionmanager
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

BMR-SS backup fails with error "the specified network name is no longer available"

We are running DPM 2012 SP1 on a Windows Server 2008 R2 system, backing up a Windows Server 2012 system that is a DC. The agent version is 4.1.3417.0. Both the DPM server and the DC are physical systems - brand new HP Proliant 360's.
When creating the replicas for the 2012 server the first time, the backups work fine, and then for a day or so after that. After a couple of days, the BMR-SS backups fail with the error "the specified network name is no longer available".
I can watch the backup happening in the Windows Server Backup console on the protected server - the BMR backup goes up to 99% and then fails. BMR backups on all the other servers are working - we have a mix of Win2008R2 and Win2012.
Here is what I have tried:
I can connect to the UNC path on the backup server without a problem during and after the backup is happening.
Tried reinstalling the DPM agent.
Tried backing up directly from the protected server to another server's network share, which worked.
I can copy multiple gigabyte files directly from the protected server to the DPM file share without a problem (the same one that DPM uses for the replica)
Tried turning off the SCEP real-time protection during the backup.
Any help would be appreciated - thanks.
KW

llo Boudewijn
I followed Boudewijn's suggestion.
The Windows 2012R2 servers had no recovery partition in disk C. I created one (400MB) following http://support.microsoft.com/kb/2930294/en-us and
DPM system restore worked. But just once.
So this is not the solution to the problem......
Is no one else having issues with DPM bare metal protection of Windows 2012R2 servers?

Financial Statement Generators fail with ORA-01722

We upgaded from 11.5.10.2 to R12.1.3. Since then we have FGSs fail with ora-01722

*+<Moderator edit - deleted MOS Doc content - pl do NOT post such content - it is a violation of your Support agreement>+*
Please refer:
R12: FSG: PERF0005 Error Detected In GET_DEF_LDGS – ORA-01403: No Data Found Common Issues [ID 1368691.1]
R12: RGRARG FSG Completes with Error, rgrsap.rgrsxp: ORA-01722: Invalid Number [ID 579655.1]

Backup Fails with Invalid RECID Error

Hi All,
Please help me to understand Caution -section
below text is from
[http://download.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmtroub.htm#447765]
Backup Fails with Invalid RECID Error: Solution 2
This solution is more difficult than solution 1:
To create the control file with SQL*Plus:
   1. Connect to the target database with SQL*Plus. For example, enter:
      % sqlplus 'SYS/oracle@trgt AS SYSDBA'
   2. Mount the database if it is not already mounted:
      SQL> ALTER DATABASE MOUNT;
   3. Back up the control file to a trace file:
      SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
   4. Edit the trace file as necessary. The relevant section of the trace file looks something like the following:
      # The following commands will create a new control file and use it
      # to open the database.
      # Data used by the recovery manager will be lost. Additional logs may
      # be required for media recovery of offline data files. Use this
      # only if the current version of all online logs are available.
      STARTUP NOMOUNT
      CREATE CONTROLFILE REUSE DATABASE "TRGT" NORESETLOGS ARCHIVELOG
      -- STANDBY DATABASE CLUSTER CONSISTENT AND UNPROTECTED
          MAXLOGFILES 32
          MAXLOGMEMBERS 2
          MAXDATAFILES 32
          MAXINSTANCES 1
          MAXLOGHISTORY 226
      LOGFILE
        GROUP 1 '/oracle/oradata/trgt/redo01.log' SIZE 25M,
        GROUP 2 '/oracle/oradata/trgt/redo02.log' SIZE 25M,
        GROUP 3 '/oracle/oradata/trgt/redo03.log' SIZE 500K
      -- STANDBY LOGFILE
      DATAFILE
        '/oracle/oradata/trgt/system01.dbf',
        '/oracle/oradata/trgt/undotbs01.dbf',
        '/oracle/oradata/trgt/cwmlite01.dbf',
        '/oracle/oradata/trgt/drsys01.dbf',
        '/oracle/oradata/trgt/example01.dbf',
        '/oracle/oradata/trgt/indx01.dbf',
        '/oracle/oradata/trgt/tools01.dbf',
        '/oracle/oradata/trgt/users01.dbf'
      CHARACTER SET WE8DEC
      # Take files offline to match current control file.
      ALTER DATABASE DATAFILE '/oracle/oradata/trgt/tools01.dbf' OFFLINE;
      ALTER DATABASE DATAFILE '/oracle/oradata/trgt/users01.dbf' OFFLINE;
      # Configure RMAN configuration record 1
      VARIABLE RECNO NUMBER;
      EXECUTE :RECNO := SYS.DBMS_BACKUP_RESTORE.SETCONFIG('CHANNEL','DEVICE TYPE DISK
      DEBUG 255');
      # Recovery is required if any of the datafiles are restored backups,
      # or if the last shutdown was not normal or immediate.
      RECOVER DATABASE
      # All logs need archiving and a log switch is needed.
      ALTER SYSTEM ARCHIVE LOG ALL;
      # Database can now be opened normally.
      ALTER DATABASE OPEN;
      # Commands to add tempfiles to temporary tablespaces.
      # Online tempfiles have complete space information.
      # Other tempfiles may require adjustment.
      ALTER TABLESPACE TEMP ADD TEMPFILE '/oracle/oradata/trgt/temp01.dbf' REUSE;
      # End of tempfile additions.
   5. Shut down the database:
      SHUTDOWN IMMEDIATE
   6. Execute the script to create the control file, recover (if necessary), archive the logs, and open the database:
      STARTUP NOMOUNT
      CREATE CONTROLFILE ...;
      EXECUTE ...;
      RECOVER DATABASE
      ALTER SYSTEM ARCHIVE LOG CURRENT;
      ALTER DATABASE OPEN ...;
Caution:
      If you do not open with the RESETLOGS option,
then two copies of an archived redo log for a given log sequence number may
exist--even though these two copies have completely different contents.
For example, one log may have been created on the original host and the other on the new host.
If you accidentally confuse the logs during a media recovery,
then the database will be corrupted but Oracle and RMAN cannot detect the problem.

Please help me to understand Caution -section
Caution:
If you do not open with the RESETLOGS option,
then two copies of an archived redo log for a given log sequence number may
exist--even though these two copies have completely different contents.
For example, one log may have been created on the original host and the other on the new host.
If you accidentally confuse the logs during a media recovery,
then the database will be corrupted but Oracle and RMAN cannot detect the problem.As per my understanding it says. If you don't open database with RESETLOGS option then there may be archived logs with log sequence number which is already archived on the source host. This may happen due to difference in RECIDs. Now when the database needs media recovery for this particular log sequence, you may provide any of them. So in this case, RMAN and Oracle will not be able to differentiate the two files and can accept any of the archived log files during recovery. Since the contents of two archived logs are different, because they are generated at different times and they contains different transactions. So, internally it corrupts your database.
Rgds.

Clone from hot backup failing with ORA-19870, 19505 unable to find backup

Similar Messages

Maybe you are looking for