Database initialisation failure

Hi all, i put this question to all you solaris heads out there. I installed Solaris 10 on a HP ML-110, and installation was a success, however upon booting into Solaris i am greeted with the above mentioned error; database initialisation failure svc.configd exited with status 102. I am only a newbie and wondering if someone can help me to create or restore one of these database repositories which it needs to successfully startup?
Any help is greatly appreciated.
Cheers, Andrew

Hi Deepali,
In case you are using g6 and above, try running the diagnostics to see all 15 tasks are complete with OK status. Then
1)check for the port your database server is using for SQL. Its by default 1433 but in case its an instance, you would need to check from the registry to see what is the exact port being used by the instance. The test would actually show you "database found" result for the default port but that might be wrong
2)make sure you run the database scripts in correct order.
Hope this helps

Similar Messages

After upgrading to Yosemite (I don't have iPhoto anymore, only PHOTOS) my pictures will not import from my iPad or iPhone 5s or any picture from web, it shows "Database Error: failured to persist version"

After upgrading to Yosemite (I don't have iPhoto anymore, only PHOTOS) my pictures will not import from my iPad or iPhone 5s or any picture from web, it shows "Database Error: failured to persist version". Any help will be greatly appreciated.

Sorry,
Yes, the error message is exactly like that ("Database error: failured to persist version")
No photos will import at all. I use USB to import from iPhone 5s or iPad 2.
About the difference? iPhoto and Photos . Are there two softwares?
I also will like to merge and/or synchronize all my photos I had saved to iCloud backups, Macbook Pro, iPhone 5s and iPad hard drives using iPhoto. It's call iPhoto library. At one point I turned off streaming.
Thanks again Larry HN.

SQL Database Login failure

I'm getting a SQL database login failure on one customer after many successful installations at other customers. My app uses OLE DB (ADO) database type with the SQLOLEDB provider to access the database. I create the table logon info structure internally in my app and use that to connect the Crystal Report for.Net framework to the database. I've verified that the server name is correct and the database allows access from SQL Management Studio and from the rest of my app, which uses VB SQL connection objects. But on this one customer I get a "Database Login" prompt when the Crystal Report is run. The prompt shows the correct user name and password. When I hit "Login" the login fails (as it failed internally leading to the dialog being shown in the first place).
Anyone have any idea on what's going on here? Any idea on where else to look? I suspect some software the customer is running is interfering somehow with Crystal Reports. But I don't have any idea of what to check for. Any help will be appreciated.
Jon Webb
PEP Systems, Inc.

Some of the more common causes for this are:
1. Firewalls - If you have a firewall between the database server and your computer
2. Different SubNets. If your database server is on a different sub-net than the computer you are trying to connnect from - then it might not be able to see it / resolve the name. To verify this, trying pinging the database computer by machine name (e.g. ping myDBServer). This can also be caused by the computer not being able to see the DNS server, and so not able to resolve the DB server machine name.
3. Wrong DB driver version. Sometimes if you are trying to connect to a newer version of SQL server using older drivers - it won't work. Verify what version of the SQL server drivers are being used.
4. MDAC is not installed. To connect via ODBC you sometimes need MDAC installed. You can check the version using the info in this kbase http://support.microsoft.com/kb/301202
Shawn

Database Initialiser does not create azure sql database

I have a WPF application In the OnStartup in the app.cs I set the Database initializer and forced the context the initialise my database:
Debug.WriteLine("Setting Initializer");
Database.SetInitializer<MyContext>(new MyDatabaseInitializer());
Debug.WriteLine("Declaring new context");
using (MyContext c = new MyContext("MyContext"))
Debug.WriteLine("Force the initialization");
c.Database.Initialize(true);
Debug.WriteLine("Done!");
I created a sql database in the management portal of the azure.
Copied the connectionstring it provided for ADO.net.
But my database is not created.
I also added a firewall rule but nothing happens. I Have no clue what to do.
Can anybody please help me with this?
If you need more information please ask i really have to get this sorted out.
Thanks in advance!

Hi Turkstra,
I have tried to use EF to create Azure SQL database, it works as expect, the database 'jambordbcreate' appear in my SQL Azure, below is the detailed codes.
using System;
using System.Collections.Generic;
using System.Data.Entity;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
namespace CodeFirst
class Program
static void Main(string[] args)
Database.SetInitializer(
new CreateDatabaseIfNotExists<SchContext>());
using (var db = new SchContext("Server=tcp:****.database.windows.net,1433;Database=jambordbcreate;User ID=vote@***;Password=***;Trusted_Connection=False;Encrypt=True;Connection Timeout=30"))
string name = "jambor";
var student=new Student(){Name=name, ID="1a"};
db.Students.Add(student);
db.SaveChanges();
db.Database.Initialize(true);
public class Student
public string ID { get; set; }
public string Name { get; set; }
public string age { get; set; }
public string sex { get; set; }
public class School
public string ID { get; set; }
public string Name { get; set; }
public virtual List<Student> Students { get; set; }
public class SchContext : DbContext
public SchContext(string connection):base(connection)
public DbSet<Student> Students { get; set; }
public DbSet<School> Schools { get; set; }
I suggest you check your SQL connection, after run your code, please refresh azure portal to see whether your database is exist. Hope this give you some help.
Best Regards,
Jambor
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.
Click
HERE to participate the survey.

Database connection failure

Hi,
In our environment we are using connection manager to connect to the database. The client connections are getting dropped intermittently and the users are getting ORA-25408 – Cannot safely replay call. The client connections are getting dropped even if the connection manager is not used and they are getting ORA-3113. I don't see any errors on alert.log, listener.log & listener.log at the time of connection drop. Even I cheked with the firewall team also. Can any one let me know what could be the cause for this?

user9114021 wrote:
The connection drop happens intermittently. The client is able to establish the connection but it is getting dropped at random points. Unable to predict when it is dropping.Okay, but you mention two different errors.
The ORA-25408 error results when your existing connection to a database instance fails over to another database instance. The root cause is the failure of the instance you're connected to. The secondary issue is that the processing that your session was busy with, cannot be failed over - and that your session needs to restart that processing from the start again.
So if this happens a lot, you have transparent app fail-over (called <i>TAF</i>) triggered a lot due to RAC db instance(s) failing regularly. This likely means relooking at your RAC configuration, setup and architecture - as something is not healthy.
25408, 00000, "can not safely replay call"
// *Cause: The connection was lost while doing this call. It may not be
//          safe to replay it after failover.
// *Action: Check to see if the results of the call have taken place, and then
//          replay it if desired.You did not mention RAC, but you did mention using Connection Manager. How are you using it and how and why is TAF configured?
The other error you mentioned is an ORA-3113.
03113, 00000, "end-of-file on communication channel"
// *Cause: The connection between Client and Server process was broken.
// *Action: There was a communication error that requires further investigation.
//          First, check for network problems and review the SQL*Net setup.
//          Also, look in the alert.log file for any errors. Finally, test to
//          see whether the server process is dead and whether a trace file
//          was generated at failure time.This error (from the client driver) means that the Oracle server process terminated without closing communication channel (tcp socket connection) to the client. The client attempted to talk to its server process and then discovered the server process is no longer there. This typically happens due to ORA-600 errors, where the Oracle server process hits an unrecoverable exception, dumps (writes a trace file and records an error in the alert log) and terminates without notifying the client.

Database Backup Failure

Hi,
We recently had a DBA here on a contract who did some work setting up backups and restores.
Unfortunately he is no longer here, and I have tried to perform a backup through OEM in his absence. The database was created by the DBA by copying the database from my development machine to a db server. On my machine some archive log files were in a directory:
C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\ARCHIVELOG
but on the server they are in the directory:
C:\APP\CS\FLASH_RECOVERY_AREA\RONNIE\ARCHIVELOG
When I am trying to run a backup from OEM, it is failing. Below is the output log. Can anyone advise?
The database is 11g.
Thanks
echo set on
connected to recovery catalog database
executing command: SET COMMAND ID
set command id to 'BACKUP_RONNIE_0000_070913105322';
connected to target database: RONNIE (DBID=2608938308, not open)
full resync complete
starting full resync of recovery catalog
allocated channel: ORA_DISK_4
channel ORA_DISK_3: SID=195 device type=DISK
backup device type disk tag 'BACKUP_RONNIE_0000_070913105322' da
allocated channel: ORA_DISK_3
allocated channel: ORA_DISK_1
Starting backup at 09-JUL-13
channel ORA_DISK_4: SID=7 device type=DISK
channel ORA_DISK_1: SID=67 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=130 device type=DISK
channel ORA_DISK_1: specifying datafile(s) in backup set
channel ORA_DISK_1: starting compressed full datafile backup set
channel ORA_DISK_1: starting piece 1 at 09-JUL-13
channel ORA_DISK_2: starting compressed full datafile backup set
input datafile file number=00001 name=C:\APP\CS\ORADATA\RONNIE\SYSTEM01.DBF
input datafile file number=00004 name=C:\APP\CS\ORADATA\RONNIE\USERS01.DBF
channel ORA_DISK_2: specifying datafile(s) in backup set
input datafile file number=00005 name=C:\APP\CS\ORADATA\RONNIE\USERS2.DBF
channel ORA_DISK_2: starting piece 1 at 09-JUL-13
channel ORA_DISK_3: specifying datafile(s) in backup set
channel ORA_DISK_3: starting compressed full datafile backup set
input datafile file number=00003 name=C:\APP\CS\ORADATA\RONNIE\UNDOTBS01.DBF
input datafile file number=00002 name=C:\APP\CS\ORADATA\RONNIE\SYSAUX01.DBF
channel ORA_DISK_3: starting piece 1 at 09-JUL-13
channel ORA_DISK_3: finished piece 1 at 09-JUL-13
channel ORA_DISK_3: backup set complete, elapsed time: 00:00:46
piece handle=C:\BACKUP\RONNIE\2013_07_09B\CAOEA6IK_1_1 tag=BACKUP_RONNIE_0000_070913105322 comment=NONE
channel ORA_DISK_1: finished piece 1 at 09-JUL-13
channel ORA_DISK_1: backup set complete, elapsed time: 00:11:21
piece handle=C:\BACKUP\RONNIE\2013_07_09B\C8OEA6IJ_1_1 tag=BACKUP_RONNIE_0000_070913105322 comment=NONE
piece handle=C:\BACKUP\RONNIE\2013_07_09B\C9OEA6IK_1_1 tag=BACKUP_RONNIE_0000_070913105322 comment=NONE
channel ORA_DISK_2: finished piece 1 at 09-JUL-13
Starting Control File and SPFILE Autobackup at 09-JUL-13
Finished backup at 09-JUL-13
channel ORA_DISK_2: backup set complete, elapsed time: 00:13:31
Finished Control File and SPFILE Autobackup at 09-JUL-13
piece handle=C:\BACKUP\RONNIE\2013_07_09B\C-2608938308-20130709-05 comment=NONE
using channel ORA_DISK_3
using channel ORA_DISK_2
using channel ORA_DISK_1
ORA-19625: error identifying file C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\ARCHIVELOG\2013_06_10\O1_MF_1_1508_8VDHNOLY_.ARC
backup device type disk tag 'BACKUP_RONNIE_0000_070913105322' ar
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 07/09/2013 11:07:46
RMAN-06059: expected archived log not found, loss of archived log compromises recoverability
using channel ORA_DISK_4
Starting backup at 09-JUL-13
allocate channel for maintenance type disk;
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Backup Piece       10540 17-MAY-13          C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\BACKUPSET\2013_05_17\O1_MF_ANNNN_BACKUP_RONN
Backup Set           10514 17-MAY-13
Backup Piece       10541 17-MAY-13          C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\BACKUPSET\2013_05_17\O1_MF_ANNNN_BACKUP_RONN
Backup Set           10515 17-MAY-13
Backup Piece       10542 17-MAY-13          C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\BACKUPSET\2013_05_17\O1_MF_ANNNN_BACKUP_RONN
Backup Set           10516 17-MAY-13
Backup Piece       10543 17-MAY-13          C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\BACKUPSET\2013_05_17\O1_MF_ANNNN_BACKUP_RONN
Backup Set           10517 17-MAY-13
Backup Piece       10544 17-MAY-13          C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\BACKUPSET\2013_05_17\O1_MF_ANNNN_BACKUP_RONN
Backup Set           10518 17-MAY-13
Backup Piece       10545 17-MAY-13          C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\BACKUPSET\2013_05_17\O1_MF_ANNNN_BACKUP_RONN
Backup Set           10519 17-MAY-13
Backup Piece       10546 17-MAY-13          C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\BACKUPSET\2013_05_17\O1_MF_ANNNN_BACKUP_RONN
Backup Set           10520 17-MAY-13
Backup Piece       10547 17-MAY-13          C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\BACKUPSET\2013_05_17\O1_MF_ANNNN_BACKUP_RONN
Backup Set           10521 17-MAY-13
Backup Piece       10548 17-MAY-13          C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\BACKUPSET\2013_05_17\O1_MF_ANNNN_BACKUP_RONN
Backup Set           10522 17-MAY-13
Backup Piece       10549 17-MAY-13          C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\BACKUPSET\2013_05_17\O1_MF_NCNNF_BACKUP_RONN
Backup Set           10523 20-MAY-13
Backup Piece       10550 20-MAY-13          C:\RMAN_BACKUP\1LOA3L40_1_1
Backup Set           10524 20-MAY-13
Backup Piece       10551 20-MAY-13          C:\RMAN_BACKUP\1MOA3L5M_1_1
Backup Set           10525 20-MAY-13
Backup Piece       10552 20-MAY-13          C:\RMAN_BACKUP\1KOA3L3F_1_1
Backup Set           10526 20-MAY-13
Backup Piece       10553 20-MAY-13          C:\RMAN_BACKUP\1JOA3L3C_1_1
Backup Set           10527 20-MAY-13
Backup Piece       10554 20-MAY-13          C:\RMAN_BACKUP\1IOA3L3C_1_1
Backup Set           10528 20-MAY-13
Backup Piece       10555 20-MAY-13          C:\RMAN_BACKUP\1NOA3NE8_1_1
Backup Set           10529 20-MAY-13
Backup Piece       10556 20-MAY-13          C:\RMAN_BACKUP\1OOA3NEA_1_1
Backup Set           10530 20-MAY-13
Backup Piece       10557 20-MAY-13          C:\RMAN_BACKUP\1QOA3NFE_1_1
Backup Set           10531 20-MAY-13
Backup Piece       10558 20-MAY-13          C:\RMAN_BACKUP\1POA3NEP_1_1
Backup Set           10532 20-MAY-13
Backup Piece       10559 20-MAY-13          C:\RMAN_BACKUP\1ROA3O5U_1_1
Backup Set           10533 10-JUN-13
Backup Piece       10560 10-JUN-13          C:\RMAN_BACKUP\27OBQVC6_1_1
Backup Set           10534 10-JUN-13
Backup Piece       10561 10-JUN-13          C:\RMAN_BACKUP\26OBQVC5_1_1
Backup Set           10535 10-JUN-13
Backup Piece       10562 10-JUN-13          C:\RMAN_BACKUP\25OBQVC5_1_1
Archive Log          11432 13-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000962_0816001666.0001
Backup Set           10536 10-JUN-13
Backup Piece       10563 10-JUN-13          C:\CONTROLFILE_BACKUP\C-2608938308-20130610-01
Archive Log          9987   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000937_0816001666.0001
Archive Log          9988   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000938_0816001666.0001
Archive Log          9989   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000939_0816001666.0001
Archive Log          9990   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000940_0816001666.0001
Archive Log          9991   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000941_0816001666.0001
Archive Log          9992   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000942_0816001666.0001
Archive Log          9993   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000943_0816001666.0001
Archive Log          9994   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000944_0816001666.0001
Archive Log          9995   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000945_0816001666.0001
Archive Log          9996   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000946_0816001666.0001
Archive Log          9997   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000947_0816001666.0001
Archive Log          9998   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000948_0816001666.0001
Archive Log          9999   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000949_0816001666.0001
Archive Log          10000 12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000950_0816001666.0001
Archive Log          10001 12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000951_0816001666.0001
Archive Log          10002 12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000952_0816001666.0001
Archive Log          10003 12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000953_0816001666.0001
Archive Log          10004 12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000954_0816001666.0001
Archive Log          10005 12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000955_0816001666.0001
Archive Log          10006 12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000956_0816001666.0001
Archive Log          10007 12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000957_0816001666.0001
Archive Log          10008 12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000958_0816001666.0001
Archive Log          10009 12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000959_0816001666.0001
Archive Log          10010 12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000960_0816001666.0001
Archive Log          10011 12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000961_0816001666.0001
Backup Set           10019 13-JUN-13
Backup Piece       10024 13-JUN-13          C:\BACKUP\RONNIE\2013_06_12\BAOC2RIC_1_1
Backup Set           10020 13-JUN-13
Backup Piece       10025 13-JUN-13          C:\BACKUP\RONNIE\2013_06_12\B8OC2RIC_1_1
Backup Set           10021 13-JUN-13
Backup Piece       10026 13-JUN-13          C:\BACKUP\RONNIE\2013_06_12\B9OC2RIC_1_1
Backup Set           10036 13-JUN-13
Backup Piece       10038 13-JUN-13          C:\APP\CS\PRODUCT\11.2.0\DBHOME_1\DATABASE\C-2608938308-20130613-00
Backup Set           10056 13-JUN-13
Backup Piece       10062 13-JUN-13          C:\BACKUP\RONNIE\2013_06_12\BCOC2SAV_1_1
Backup Set           10057 13-JUN-13
Backup Piece       10063 13-JUN-13          C:\BACKUP\RONNIE\2013_06_12\BDOC2SAV_1_1
Backup Set           10058 13-JUN-13
Backup Piece       10064 13-JUN-13          C:\BACKUP\RONNIE\2013_06_12\BEOC2SB1_1_1
Backup Set           10059 13-JUN-13
Backup Piece       10065 13-JUN-13          C:\BACKUP\RONNIE\2013_06_12\BFOC2SC1_1_1
Backup Set           10135 13-JUN-13
Backup Piece       10152 13-JUN-13          C:\APP\CS\PRODUCT\11.2.0\DBHOME_1\DATABASE\C-2608938308-20130613-01
Backup Set           10181 13-JUN-13
Backup Piece       10186 13-JUN-13          C:\BACKUP\RONNIE\2013_06_13\BJOC3A4C_1_1
Backup Set           10182 13-JUN-13
Backup Piece       10187 13-JUN-13          C:\BACKUP\RONNIE\2013_06_13\BHOC3A4B_1_1
Backup Set           10183 13-JUN-13
Backup Piece       10188 13-JUN-13          C:\BACKUP\RONNIE\2013_06_13\BIOC3A4C_1_1
Archive Log          10504 10-JUN-13          C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\ARCHIVELOG\2013_06_10\O1_MF_1_1508_8VDHNOLY_
Backup Set           10198 13-JUN-13
Backup Piece       10200 13-JUN-13          C:\BACKUP\RONNIE\2013_06_13\C-2608938308-20130613-02
Archive Log          10505 10-JUN-13          C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\ARCHIVELOG\2013_06_10\O1_MF_1_1509_8VDNV9RQ_
Archive Log          10506 11-JUN-13          C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\ARCHIVELOG\2013_06_11\O1_MF_1_1510_8VDV5831_
Archive Log          10507 12-JUN-13          C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\ARCHIVELOG\2013_06_12\O1_MF_1_1511_8VHHNROJ_
Archive Log          10508 12-JUN-13          C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\ARCHIVELOG\2013_06_12\O1_MF_1_1512_8VJXYTOD_
Archive Log          10509 13-JUN-13          C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\ARCHIVELOG\2013_06_13\O1_MF_1_1513_8VM9449J_
Backup Set           10510 01-MAY-13
Backup Piece       10537 01-MAY-13          C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\BACKUPSET\2013_05_01\O1_MF_NNNDF_BACKUP_RONN
Backup Set           10511 01-MAY-13
Backup Piece       10538 01-MAY-13          C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\BACKUPSET\2013_05_01\O1_MF_ANNNN_BACKUP_RONN
Backup Set           10512 17-MAY-13
Backup Piece       10539 17-MAY-13          C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\BACKUPSET\2013_05_17\O1_MF_NCSNF_BACKUP_RONN
Backup Set           10513 17-MAY-13
Backup Set           9751   11-JUN-13
Backup Piece       9758   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\ARCHIVELOG\RONNIE_ARCHIVE_LOG_349_1_817839774.BKP
Backup Set           9752   11-JUN-13
Backup Piece       9759   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\ARCHIVELOG\RONNIE_ARCHIVE_LOG_348_1_817839769.BKP
Backup Set           9753   11-JUN-13
Backup Piece       9760   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\ARCHIVELOG\RONNIE_ARCHIVE_LOG_347_1_817839768.BKP
Backup Set           9754   11-JUN-13
Backup Piece       9761   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\ARCHIVELOG\RONNIE_ARCHIVE_LOG_350_1_817839785.BKP
Archive Log          9797   11-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000897_0816001666.0001
Backup Set           9779   11-JUN-13
Backup Piece       9782   11-JUN-13          C:\APP\CS\PRODUCT\11.2.0\DBHOME_1\DATABASE\C-2608938308-20130611-01
Archive Log          9798   11-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000898_0816001666.0001
Backup Set           9808   11-JUN-13
Backup Piece       9815   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\ARCHIVELOG\RONNIE_ARCHIVE_LOG_352_1_817839885.BKP
Backup Set           9809   11-JUN-13
Backup Piece       9816   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\ARCHIVELOG\RONNIE_ARCHIVE_LOG_354_1_817839887.BKP
Backup Set           9810   11-JUN-13
Backup Piece       9817   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\ARCHIVELOG\RONNIE_ARCHIVE_LOG_355_1_817839891.BKP
Backup Set           9811   11-JUN-13
Backup Piece       9818   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\ARCHIVELOG\RONNIE_ARCHIVE_LOG_353_1_817839885.BKP
Backup Set           9812   11-JUN-13
Backup Piece       9819   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\ARCHIVELOG\RONNIE_ARCHIVE_LOG_356_1_817839906.BKP
Archive Log          9874   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000899_0816001666.0001
Backup Set           9839   11-JUN-13
Backup Piece       9844   11-JUN-13          C:\APP\CS\PRODUCT\11.2.0\DBHOME_1\DATABASE\C-2608938308-20130611-02
Archive Log          9875   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000900_0816001666.0001
Archive Log          9876   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000901_0816001666.0001
Archive Log          9877   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000902_0816001666.0001
Archive Log          9953   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000903_0816001666.0001
Backup Set           9878   12-JUN-13
Backup Piece       9881   12-JUN-13          C:\APP\CS\PRODUCT\11.2.0\DBHOME_1\DATABASE\C-2608938308-20130612-00
Archive Log          9954   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000904_0816001666.0001
Archive Log          9955   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000905_0816001666.0001
Archive Log          9956   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000906_0816001666.0001
Archive Log          9957   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000907_0816001666.0001
Archive Log          9958   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000908_0816001666.0001
Archive Log          9959   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000909_0816001666.0001
Archive Log          9960   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000910_0816001666.0001
Archive Log          9961   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000911_0816001666.0001
Archive Log          9962   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000912_0816001666.0001
Archive Log          9963   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000913_0816001666.0001
Archive Log          9964   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000914_0816001666.0001
Archive Log          9965   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000915_0816001666.0001
Archive Log          9966   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000916_0816001666.0001
Archive Log          9967   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000917_0816001666.0001
Archive Log          9968   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000918_0816001666.0001
Archive Log          9969   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000919_0816001666.0001
Archive Log          9970   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000920_0816001666.0001
Archive Log          9971   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000922_0816001666.0001
Archive Log          9972   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000921_0816001666.0001
Archive Log          9973   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000923_0816001666.0001
Archive Log          9974   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000924_0816001666.0001
Archive Log          9975   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000925_0816001666.0001
Archive Log          9976   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000926_0816001666.0001
Archive Log          9977   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000927_0816001666.0001
Archive Log          9978   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000928_0816001666.0001
Archive Log          9979   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000930_0816001666.0001
Archive Log          9980   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000929_0816001666.0001
Archive Log          9981   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000931_0816001666.0001
Archive Log          9982   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000932_0816001666.0001
Archive Log          9983   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000933_0816001666.0001
Archive Log          9984   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000934_0816001666.0001
Archive Log          9985   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000935_0816001666.0001
Archive Log          9986   12-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000936_0816001666.0001
Backup Set           9522   10-JUN-13
Backup Piece       9530   10-JUN-13          C:\BACKUP\RONNIE\2013_06_10\DATABASE\RONNIE_FULL_ONLINE_DB_323_3_817752171.BKP
Backup Set           9522   10-JUN-13
Backup Piece       9529   10-JUN-13          C:\BACKUP\RONNIE\2013_06_10\DATABASE\RONNIE_FULL_ONLINE_DB_323_2_817752171.BKP
Backup Set           9522   10-JUN-13
Backup Piece       9528   10-JUN-13          C:\BACKUP\RONNIE\2013_06_10\DATABASE\RONNIE_FULL_ONLINE_DB_323_1_817752171.BKP
Archive Log          9557   10-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000891_0816001666.0001
Backup Set           9542   10-JUN-13
Backup Piece       9544   10-JUN-13          C:\APP\CS\PRODUCT\11.2.0\DBHOME_1\DATABASE\C-2608938308-20130610-00
Archive Log          9558   10-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000892_0816001666.0001
Backup Set           9568   10-JUN-13
Backup Piece       9574   10-JUN-13          C:\BACKUP\RONNIE\2013_06_10\ARCHIVELOG\RONNIE_ARCHIVE_LOG_326_1_817753203.BKP
Backup Set           9569   10-JUN-13
Backup Piece       9575   10-JUN-13          C:\BACKUP\RONNIE\2013_06_10\ARCHIVELOG\RONNIE_ARCHIVE_LOG_329_1_817753216.BKP
Backup Set           9570   10-JUN-13
Backup Piece       9576   10-JUN-13          C:\BACKUP\RONNIE\2013_06_10\ARCHIVELOG\RONNIE_ARCHIVE_LOG_328_1_817753211.BKP
Backup Set           9571   10-JUN-13
Backup Piece       9577   10-JUN-13          C:\BACKUP\RONNIE\2013_06_10\ARCHIVELOG\RONNIE_ARCHIVE_LOG_327_1_817753209.BKP
Archive Log          9610   10-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000893_0816001666.0001
Backup Set           9591   10-JUN-13
Backup Piece       9595   10-JUN-13          C:\APP\CS\PRODUCT\11.2.0\DBHOME_1\DATABASE\C-2608938308-20130610-01
Archive Log          9611   10-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000894_0816001666.0001
Backup Set           9621   10-JUN-13
Backup Piece       9628   10-JUN-13          C:\BACKUP\RONNIE\2013_06_10\ARCHIVELOG\RONNIE_ARCHIVE_LOG_331_1_817753347.BKP
Backup Set           9622   10-JUN-13
Backup Piece       9629   10-JUN-13          C:\BACKUP\RONNIE\2013_06_10\ARCHIVELOG\RONNIE_ARCHIVE_LOG_334_1_817753349.BKP
Backup Set           9623   10-JUN-13
Backup Piece       9630   10-JUN-13          C:\BACKUP\RONNIE\2013_06_10\ARCHIVELOG\RONNIE_ARCHIVE_LOG_333_1_817753349.BKP
Backup Set           9624   10-JUN-13
Backup Piece       9631   10-JUN-13          C:\BACKUP\RONNIE\2013_06_10\ARCHIVELOG\RONNIE_ARCHIVE_LOG_332_1_817753348.BKP
Backup Set           9625   10-JUN-13
Backup Piece       9632   10-JUN-13          C:\BACKUP\RONNIE\2013_06_10\ARCHIVELOG\RONNIE_ARCHIVE_LOG_335_1_817753372.BKP
Backup Set           9648   10-JUN-13
Backup Piece       9650   10-JUN-13          C:\APP\CS\PRODUCT\11.2.0\DBHOME_1\DATABASE\C-2608938308-20130610-02
Backup Set           9672   11-JUN-13
Backup Piece       9679   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\DATABASE\RONNIE_FULL_ONLINE_DB_337_1_817838604.BKP
Backup Set           9673   11-JUN-13
Backup Piece       9680   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\DATABASE\RONNIE_FULL_ONLINE_DB_340_1_817838605.BKP
Backup Set           9674   11-JUN-13
Backup Piece       9681   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\DATABASE\RONNIE_FULL_ONLINE_DB_341_1_817838615.BKP
Backup Set           9675   11-JUN-13
Backup Piece       9682   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\DATABASE\RONNIE_FULL_ONLINE_DB_339_1_817838604.BKP
Backup Set           9676   11-JUN-13
Backup Piece       9683   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\DATABASE\RONNIE_FULL_ONLINE_DB_338_1_817838604.BKP
Backup Set           9700   11-JUN-13
Backup Piece       9706   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\DATABASE\RONNIE_FULL_ONLINE_DB_344_1_817838622.BKP
Backup Set           9701   11-JUN-13
Backup Piece       9709   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\DATABASE\RONNIE_FULL_ONLINE_DB_342_3_817838621.BKP
Backup Set           9701   11-JUN-13
Backup Piece       9708   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\DATABASE\RONNIE_FULL_ONLINE_DB_342_2_817838621.BKP
Backup Set           9701   11-JUN-13
Backup Piece       9707   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\DATABASE\RONNIE_FULL_ONLINE_DB_342_1_817838621.BKP
Backup Set           9702   11-JUN-13
Backup Piece       9712   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\DATABASE\RONNIE_FULL_ONLINE_DB_343_3_817838621.BKP
Backup Set           9702   11-JUN-13
Backup Piece       9711   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\DATABASE\RONNIE_FULL_ONLINE_DB_343_2_817838621.BKP
Backup Set           9702   11-JUN-13
Backup Piece       9710   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\DATABASE\RONNIE_FULL_ONLINE_DB_343_1_817838621.BKP
Archive Log          9739   11-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000896_0816001666.0001
Backup Set           9724   11-JUN-13
Backup Piece       9726   11-JUN-13          C:\APP\CS\PRODUCT\11.2.0\DBHOME_1\DATABASE\C-2608938308-20130611-00
Archive Log          9740   11-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000895_0816001666.0001
Backup Set           9750   11-JUN-13
Backup Piece       9757   11-JUN-13          C:\BACKUP\RONNIE\2013_06_11\ARCHIVELOG\RONNIE_ARCHIVE_LOG_346_1_817839767.BKP
released channel: ORA_DISK_1
released channel: ORA_DISK_2
released channel: ORA_DISK_3
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
Backup Set           7344   07-JUN-13
Backup Piece       7365   07-JUN-13          C:\BACKUP\RONNIE\2013_06_07\DATABASE\RONNIE_FULL_ONLINE_DB_223_1_817497520.BKP
Backup Set           7345   07-JUN-13
Backup Piece       7368   07-JUN-13          C:\BACKUP\RONNIE\2013_06_07\DATABASE\RONNIE_FULL_ONLINE_DB_221_3_817497519.BKP
Backup Set           7345   07-JUN-13
Backup Piece       7367   07-JUN-13          C:\BACKUP\RONNIE\2013_06_07\DATABASE\RONNIE_FULL_ONLINE_DB_221_2_817497519.BKP
Backup Set           7345   07-JUN-13
Backup Piece       7366   07-JUN-13          C:\BACKUP\RONNIE\2013_06_07\DATABASE\RONNIE_FULL_ONLINE_DB_221_1_817497519.BKP
Archive Log          7398   07-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000885_0816001666.0001
Backup Set           7346   07-JUN-13
Backup Piece       7371   07-JUN-13          C:\BACKUP\RONNIE\2013_06_07\DATABASE\RONNIE_FULL_ONLINE_DB_222_3_817497520.BKP
Backup Set           7346   07-JUN-13
Backup Piece       7370   07-JUN-13          C:\BACKUP\RONNIE\2013_06_07\DATABASE\RONNIE_FULL_ONLINE_DB_222_2_817497520.BKP
Backup Set           7346   07-JUN-13
Backup Piece       7369   07-JUN-13          C:\BACKUP\RONNIE\2013_06_07\DATABASE\RONNIE_FULL_ONLINE_DB_222_1_817497520.BKP
Archive Log          7399   07-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000884_0816001666.0001
Archive Log          8426   07-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000886_0816001666.0001
Backup Set           7453   07-JUN-13
Backup Piece       7500   07-JUN-13          C:\BACKUP\RONNIE\2013_06_07\ARCHIVELOG\RONNIE_ARCHIVE_LOG_269_1_817502288.BKP
Archive Log          8427   07-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000887_0816001666.0001
Backup Set           8480   07-JUN-13
Backup Piece       8528   07-JUN-13          C:\BACKUP\RONNIE\2013_06_07\ARCHIVELOG\RONNIE_ARCHIVE_LOG_316_1_817506665.BKP
Backup Set           8482   07-JUN-13
Backup Piece       8530   07-JUN-13          C:\BACKUP\RONNIE\2013_06_07\ARCHIVELOG\RONNIE_ARCHIVE_LOG_315_1_817506560.BKP
Archive Log          9458   07-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000888_0816001666.0001
Backup Set           9422   07-JUN-13
Backup Piece       9443   07-JUN-13          C:\APP\CS\PRODUCT\11.2.0\DBHOME_1\DATABASE\C-2608938308-20130607-02
Archive Log          9459   09-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000889_0816001666.0001
Archive Log          9486   10-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000890_0816001666.0001
Backup Set           9498   10-JUN-13
Backup Piece       9504   10-JUN-13          C:\BACKUP\RONNIE\2013_06_10\DATABASE\RONNIE_FULL_ONLINE_DB_319_1_817752151.BKP
Backup Set           9499   10-JUN-13
Backup Piece       9505   10-JUN-13          C:\BACKUP\RONNIE\2013_06_10\DATABASE\RONNIE_FULL_ONLINE_DB_318_1_817752151.BKP
Backup Set           9500   10-JUN-13
Backup Piece       9506   10-JUN-13          C:\BACKUP\RONNIE\2013_06_10\DATABASE\RONNIE_FULL_ONLINE_DB_320_1_817752152.BKP
Backup Set           9501   10-JUN-13
Backup Piece       9507   10-JUN-13          C:\BACKUP\RONNIE\2013_06_10\DATABASE\RONNIE_FULL_ONLINE_DB_321_1_817752152.BKP
Backup Set           9520   10-JUN-13
Backup Piece       9524   10-JUN-13          C:\BACKUP\RONNIE\2013_06_10\DATABASE\RONNIE_FULL_ONLINE_DB_324_1_817752172.BKP
Backup Set           9521   10-JUN-13
Backup Piece       9527   10-JUN-13          C:\BACKUP\RONNIE\2013_06_10\DATABASE\RONNIE_FULL_ONLINE_DB_322_3_817752171.BKP
Backup Set           9521   10-JUN-13
Backup Piece       9526   10-JUN-13          C:\BACKUP\RONNIE\2013_06_10\DATABASE\RONNIE_FULL_ONLINE_DB_322_2_817752171.BKP
Backup Set           9521   10-JUN-13
Backup Piece       9525   10-JUN-13          C:\BACKUP\RONNIE\2013_06_10\DATABASE\RONNIE_FULL_ONLINE_DB_322_1_817752171.BKP
Archive Log          11570 30-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000138_0818004327.0001
Archive Log          11571 01-JUL-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000139_0818004327.0001
Archive Log          11572 02-JUL-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000140_0818004327.0001
Archive Log          11573 03-JUL-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000141_0818004327.0001
Archive Log          11574 03-JUL-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000142_0818004327.0001
Archive Log          11575 04-JUL-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000143_0818004327.0001
Archive Log          11576 04-JUL-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000144_0818004327.0001
Archive Log          11577 05-JUL-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000145_0818004327.0001
Archive Log          11578 06-JUL-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000146_0818004327.0001
Archive Log          11579 07-JUL-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000147_0818004327.0001
Archive Log          11580 07-JUL-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000148_0818004327.0001
Backup Set           11594 13-JUN-13
Backup Piece       11608 13-JUN-13          C:\BACKUP\RONNIE\2013_06_13\C-2608938308-20130613-03
Backup Set           11699 08-JUL-13
Backup Piece       11704 08-JUL-13          C:\BACKUP\RONNIE\2013_07_08\BOOE81TB_1_1
Backup Set           11700 08-JUL-13
Backup Piece       11705 08-JUL-13          C:\BACKUP\RONNIE\2013_07_08\BMOE81TB_1_1
Backup Set           11701 08-JUL-13
Backup Piece       11706 08-JUL-13          C:\BACKUP\RONNIE\2013_07_08\BNOE81TB_1_1
Archive Log          11757 08-JUL-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000149_0818004327.0001
Backup Set           11716 08-JUL-13
Backup Piece       11718 08-JUL-13          C:\BACKUP\RONNIE\2013_06_13\C-2608938308-20130708-00
Archive Log          11758 08-JUL-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000150_0818004327.0001
Backup Set           11759 09-JUL-13
Backup Piece       11762 09-JUL-13          C:\BACKUP\RONNIE\2013_06_13\C-2608938308-20130709-00
Backup Set           11789 09-JUL-13
Backup Piece       11791 09-JUL-13          C:\BACKUP\RONNIE\2013_07_09\C-2608938308-20130709-01
Archive Log          11540 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000108_0818004327.0001
Archive Log          11541 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000109_0818004327.0001
Archive Log          11542 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000110_0818004327.0001
Archive Log          11543 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000111_0818004327.0001
Archive Log          11544 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000112_0818004327.0001
Archive Log          11545 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000113_0818004327.0001
Archive Log          11546 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000114_0818004327.0001
Archive Log          11547 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000115_0818004327.0001
Archive Log          11548 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000116_0818004327.0001
Backup Set           11813 09-JUL-13
Backup Piece       11816 09-JUL-13          C:\BACKUP\RONNIE\2013_07_09\C-2608938308-20130709-02
delete noprompt obsolete device type disk;
channel ORA_MAINT_DISK_1: SID=67 device type=DISK
allocated channel: ORA_MAINT_DISK_1
released channel: ORA_DISK_4
Archive Log          11501 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000069_0818004327.0001
Archive Log          11502 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000070_0818004327.0001
Archive Log          11503 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000071_0818004327.0001
Archive Log          11504 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000072_0818004327.0001
Archive Log          11505 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000073_0818004327.0001
Archive Log          11506 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000074_0818004327.0001
Archive Log          11507 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000076_0818004327.0001
Archive Log          11508 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000075_0818004327.0001
Archive Log          11509 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000078_0818004327.0001
Archive Log          11510 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000077_0818004327.0001
Archive Log          11511 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000079_0818004327.0001
Archive Log          11512 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000080_0818004327.0001
Archive Log          11513 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000081_0818004327.0001
Archive Log          11514 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000082_0818004327.0001
Archive Log          11515 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000083_0818004327.0001
Archive Log          11516 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000084_0818004327.0001
Archive Log          11517 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000085_0818004327.0001
Archive Log          11518 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000086_0818004327.0001
Archive Log          11519 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000087_0818004327.0001
Archive Log          11520 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000088_0818004327.0001
Archive Log          11521 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000090_0818004327.0001
Archive Log          11522 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000089_0818004327.0001
Archive Log          11523 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000091_0818004327.0001
Archive Log          11524 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000092_0818004327.0001
Archive Log          11525 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000093_0818004327.0001
Archive Log          11526 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000094_0818004327.0001
Archive Log          11527 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000095_0818004327.0001
Archive Log          11528 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000096_0818004327.0001
Archive Log          11529 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000097_0818004327.0001
Archive Log          11530 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000098_0818004327.0001
Archive Log          11531 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000099_0818004327.0001
Archive Log          11532 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000100_0818004327.0001
Archive Log          11533 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000101_0818004327.0001
Archive Log          11534 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000102_0818004327.0001
Archive Log          11535 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000103_0818004327.0001
Archive Log          11536 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000104_0818004327.0001
Archive Log          11537 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000105_0818004327.0001
Archive Log          11538 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000106_0818004327.0001
Archive Log          11539 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000107_0818004327.0001
Archive Log          11487 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000055_0818004327.0001
Archive Log          11488 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000056_0818004327.0001
Archive Log          11489 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000057_0818004327.0001
Archive Log          11490 27-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000058_0818004327.0001
Archive Log          11549 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000117_0818004327.0001
Archive Log          11550 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000118_0818004327.0001
Archive Log          11551 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000119_0818004327.0001
Archive Log          11552 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000120_0818004327.0001
Archive Log          11553 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000121_0818004327.0001
Archive Log          11554 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000122_0818004327.0001
Archive Log          11555 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000123_0818004327.0001
Archive Log          11556 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000124_0818004327.0001
Archive Log          11557 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000125_0818004327.0001
Archive Log          11558 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000126_0818004327.0001
Archive Log          11559 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000127_0818004327.0001
Archive Log          11560 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000128_0818004327.0001
Archive Log          11561 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000129_0818004327.0001
Archive Log          11562 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000130_0818004327.0001
Archive Log          11563 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000131_0818004327.0001
Archive Log          11564 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000132_0818004327.0001
Archive Log          11565 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000133_0818004327.0001
Archive Log          11566 28-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000134_0818004327.0001
Archive Log          11567 29-JUN-13          C:\APP\CS\ARCHIVELOG\RONNIE\ARC0000000135_0818004327.0001
Archive Log          11568 2

Hi,
Have You change Anything in database receltelly , your Error is
ORA-19625: error identifying file C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\ARCHIVELOG\2013_06_10\O1_MF_1_1508_8VDHNOLY_.ARC
     backup device type disk tag 'BACKUP_RONNIE_0000_070913105322' ar
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 07/09/2013 11:07:46
RMAN-06059: expected archived log not found, loss of archived log compromises recoverability
using channel ORA_DISK_4
Starting backup at 09-JUL-13
allocate channel for maintenance type disk;
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
rman not able to find the archive log file at path C:\APP\RM\FLASH_RECOVERY_AREA\RONNIE\ARCHIVELOG\2013_06_10\O1_MF_1_1508_8VDHNOLY_.ARC
which can be mandatory for the recovery of that backup set , try to find out the file..

SQL Server 2008 Database Mail Failure

I am currently using SQL Server 2008. I have database mail setup and it was working for a while without any issues. However, now we are getting the following message anytime it trys to send an email with a domain address other than our own.
The mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 4 (2010-07-21T15:21:58). Exception Message: Cannot send mails to mail server. (The operation has timed out.). )
The emails have been setup and working since last year up until June 30th. I have made sure that the server name for the email server is correct. Ports 25, 110, and 443 are open on the email server and I setup the database mail to use port 25.
The sever name is webmail.somecompanyname.com
I tested on the server that I could telnet to the mail server and I get the response back from the server that says ready.
I tested sending an email to my work address by right clicking database mail and send test e-mail. When I send it to my work email it works fine (myname.somecompany.com)
When I do the same test only sending it to my personal comcast account I get the error message in the
sysmail_faileditems.
Can anyone help shed some light on other possible issues that might be causing this to fail now?
Any help is greatly appreciated.
Thanks in advance.

My issues with the email might be fixed now. I will be keeping an eye on it today.
It turns out that we have 2 IPs for the 2 different internet providers that we have for our company.
In the
On Mail server > Exchange Server Manager > SMTP Connector Properties
> Access Properties > Access Tab > Relay button it had the ip address for one of the providers, but not for the comcast one that we just installed on June 30th.
The network administrator added the ip for comcast to the location above and it seems to be working now.
We will keep our fingers crossed.
Thanks for all your suggestions.

Testdrive N4S with Fedora 8 - Database Start failure

Hello,
I installed the System N4S successfully on a Fedora 8, kernel 2.6.23, but Database start ends up with failure.
Message from startdb.log:
Starting XServer
    12916 XSERVER Found other running x_server with version 'X64/LINUX 7.6.00   Build 018-123-119-055'
    12902 XSERVER started, 'already...'
So 30. Dez 19:01:41 CET 2007
Starting database
Starting Database Instance...
Error! XUser not found!
Opening Database...
Error! XUser not found!
DB-log Files indicate some missing crypt-libs:
trc file: "/sapdb/data/wrk/niserver_machine64.trace", trc level: 1, release: "700"
Sun Dec 30 18:13:50 2007
ERROR => DlLoadLib: dlopen()= /sapdb/programs/lib/libsapcrypto.so: cannot open shared object file: No such file or directory -> DLENOACCESS (0,Success) [dlux.c       314]
ERROR => CDKLoadSAPCryptModule: Loading of /sapdb/programs/lib/libsapcrypto.so failed! [cdkapi.c     204]
This library was obviously not included in the testdrive.
However this seems to result only in a warning and to be not the real problem.
I saw somewhere already a comment advising an upgrade of the database-version because of some library conflicts with an other problem:
https://forums.sdn.sap.com/click.jspa?searchID=7692305&messageID=3719866
Can somebody advise on that topic?
Thank you and kind regards,
Axel

Dear Axel,
having no XUSERs (needed for database connection) makes an automated database start impossible. Can you check, if you have a XUSER file in the home directory of n4sadm?
$> su - n4sadm
#> cd
#> ls -la .XUSER.62
-rw------- 1 n4sadm sapsys 1724 Apr 20 2007 .XUSER.62
If it is there, but you can't connect to the database, it should make a copy of the old one with:
mv -a .XUSER.62 .XUSER.62.org
and create a new one, which you should do if the file isn't there as well:
/sapdb/programs/bin/xuser -U DEFAULT -u sapn4s,sapn4sadm -d N4S -n n4shost -S SAPR3 -t 0 -I 0 set
/sapdb/programs/bin/xuser -U c -u control,sapn4sadm -d N4S -n n4shost -S SAPR3 -t 0 -I 0 set
/sapdb/programs/bin/xuser -U c_J2EE -u control,sapn4sadm -d N4S -n n4shost -S SAPR3 -t 0 -I 0 set
/sapdb/programs/bin/xuser -U w -u superdba,sapn4sadm -d N4S -n n4shost -S SAPR3 -t 0 -I 0 set
After executing the 4 commands, a new .XUSER.62 file will be there, which allows you to start the database.
Thanks,
Hannes

Siebel Database disk failure

Dear Members,
We have a major disk failure on our development environment's data base server.
It seems to be, the data base has got corrupted.But our Siebel server is installed on a different machine. I have the backup of the repository .dat file with me.
We do not have the full backup of this DB server as this is a DEV environment. In our Client's Organization, as per policy no DEV environment are included in backup process.
Once our DBA re-install the DB. What all the steps we need to follow to make the environment as earlier.
As per my knowledge, I am planning to do the following things.
1) Create the SBL_DATA and SBL_INDX table spaces.
2) Execute grantusr.sql script.
So after these things, what I need to do.
Please suggest.
Regards
Vamshi

Hi Vamshi,
This is a very serious issue and probably you may try the following approach:
1. Install the Siebel Database and select new database.
2. Once installed add a developer user on the database and execute the grantusr.sql
3. In the database execute an update statement and update all the Object Locked columns and Object Locked By columns with value as 'Y' and developers' row_id respectively.
4. In the Developer's Local DBF file lock all the projects and tell him to do a check-in.
I am not sure whether the above will work well for you as I have tried this only once and that too in a proto environment. Also the developer should be having a reasonably recent DBF.
Please update if this approach works for you.
With Regards,
Tanmay Jain

JControl.exe does not start...Database Initialisation Problem...MS SQL

Hi,
I was wondering if anyone has any idea on why JCONTROL.exe does not start. I am currently installing NW04s EP7. The DB is on another host and te SCS and CI are on a different host. I am going throught the installation when I get the following error fro the Bootstrap file.
I have already done the following steps:
1. entered the SAP<SID>DB password
2. SQL is started and running on the second host.
3. The bootstrap.propeties files look the same as any other file EP system on our network
[Mar 7, 2007 5:32:35 PM ] [Bootstrap module]> Problem occurred while performing synchronization.
[Mar 7, 2007 5:35:45 PM ] -
[Mar 7, 2007 5:35:45 PM ] Bootstrap MODE:
[Mar 7, 2007 5:35:45 PM ] <INSTANCE GLOBALS>
[Mar 7, 2007 5:35:45 PM ] determined by parameter [ID0117060].
[Mar 7, 2007 5:35:45 PM ] -
[Mar 7, 2007 5:35:46 PM ] Exception occurred:
com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
     at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:422)
     at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
     at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
==[ Caused by: ]==----
com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred: Secure Store lib Dir does not exist
PC04315\sapmnt\ET1\SYS\global\security\lib\tools
     at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:212)
     at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)
     at com.sap.engine.bootstrap.Synchronizer.<init>(Synchronizer.java:60)
     at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:419)
     at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
     at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
[Mar 7, 2007 5:35:46 PM ] [Bootstrap module]> Problem occurred while performing synchronization.
Many thanks,
Adil Zafar

==[ Caused by: ]==----
com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred: Secure Store lib Dir does not exist
PC04315\sapmnt\ET1\SYS\global\security\lib\tools
Do you have strong encryption on your current system?

Database link failure.

Using the grouper account, I have a database link defined as follows:
CREATE PUBLIC DATABASE LINK parent_link
CONNECT TO parent IDENTIFIED BY "password"
USING 'rem1';
... and several synonyms, one of which is defined as follows:
CREATE PUBLIC SYNONYM valid_fishery FOR parent.valid_fishery@parent_link;
I am able to log in as parent in SQL Plus and Select from valid_fishery.
But when logged in as grouper, I could not Select from valid_fishery, using either method of access:
Referenceing the table name: Select * from parent.valid_fishery@parent_link;
Referenceing the synonym: Select * from valid_fishery;
I get the message:
ORA-01017: invalid username/password; logon denied.
ORA-02063: preceding line from PARENT_LINK
This message is obviously wrong because I logged in through SQL Plus with the exact same username/password.
Clearly, something is wrong with the link, but what could it be?
Edited by: Prohan on Sep 23, 2009 9:33 AM

Proham,
I have seen various issues when going downward across database links (from a higher version of database, to a lower version of database). This has been probablematic over the years in various versions and with different commands that are typically fixed.
Sometimes, in the past, I have seen incorrect errors raised over db_link issues. I believe I even recall selecting from 'dual' returned an error, or when running certain commands using a procedure or package on the remote database.
First thing I'd ask to check (even though it does not seem related), is to ensure either grouper, (or public) have select access to 'parent's' tables.
Does grouper have an account in the remote database? This shouldn't matter actually since you created the link to connect to through parent.

Need help urgent!! regarding Database connection failure

Hi Experts,
when i try to login sqlplus...i came across with this error 'TNS adaptor error'
as i try to restart the services i dont have the sufficient privilages to start.
Mean while, i have another database in my another system. i know the port number ,host name and all...
can i connect from one system to another using the port number,host name..
If So, can any one help me pls

Hi Bhargav,
check $ORACLE_HOME $PATH and $ORACLE_SID is correct?
what OS? windows need service privileges, contact admin.
can i connect from one system to another using the port number,host name..yes, and login info.
--sgc

Upgrading iPhoto database EPIC FAILURE

Since upgrading to Yosemite a few months ago I can't successfully upgrade my iPhoto database. It gets about 95% done and then goes no further. It does not fail but does not complete. I have let it go as long as 48 hours. I have tried this at least ten times. In the end I have force quit. How can I ever get iPhoto to open again?

Your db is corrupted.
Option 1
Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Repair Database. If that doesn't help, then try again, this time using Rebuild Database.
If that fails:
Option 2
Download iPhoto Library Manager and use its rebuild function. (In early versions of Library Manager it's the File -> Rebuild command. In later versions it's under the Library menu.)
This will create an entirely new library. It will then copy (or try to) your photos and all the associated metadata and versions to this new Library, and arrange it as close as it can to what you had in the damaged Library. It does this based on information it finds in the iPhoto sharing mechanism - but that means that things not shared won't be there, so no slideshows, books or calendars, for instance - but it should get all your events, albums and keywords, faces and places back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.
Regards
TD

Oracle 9i database download failure

I am not able to download the oracle 9i database disk 1 file i.e. 92010NT_Disk1.zip (612802971 bytes). Plz help me out.

Hi
de symcjic.dll generates problems in server with PENTIUM IV procceses.
Please, check into Metalink the Technical Note 1507946.1, maybe it´d can help yuo
good luck

Database Adapter Failure - 10.1.3.1

Added a database adapter in 10.1.3.1 to call a package which calls successfully from 10.1.2.0.2.
When I run it under 10.1.3.1, I get an error saying that an element cannot be NULL, and on investigation I see that BPEL is adding in the wrong namespace, i.e. xmlns="" on each element, and hence it cannot find the element.
<messages><input><Invoke_2_test_InputVariable><part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="InputParameters"><InputParameters xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/WIP/TEST/">
<P_BPEL_TASK_ID xmlns="">10011</P_BPEL_TASK_ID>
<P_BPEL_PROCESS xmlns="">test2</P_BPEL_PROCESS>
<P_BPEL_STEP xmlns="">test2</P_BPEL_STEP>
<P_PAYLOAD xmlns=""/>
</InputParameters>
Why is BPEL adding in this xmlns="" on each element? It does not occur in 10.1.2.0.2.
Pete

DOM Level 2 has replaced DOM Level 1. The XSDs that the stored procedure adapter generates will include elementFormDefault="qualified". These changes will be available in the upcoming 10.1.3.3.0 patch set.

Database initialisation failure

Similar Messages

Maybe you are looking for