tablespace PSAPSR3 is already in backup status

[Former Member]

Hi!

I have planed an ALL-ONLINE Backup from DB13.

What does it mean and how can I proceed to backuo these tablespaces?

Here is the error I am getting:

BR0328E Database file E:\ORACLE\DEV\SAPDATA1\SR3_1\SR3.DATA1 of tablespace PSAPSR3 is already in backup status

BR0328E Database file E:\ORACLE\DEV\SAPDATA1\SR3_2\SR3.DATA2 of tablespace PSAPSR3 is already in backup status

.............................................................................

And second question:

<b>Which form should have the parameter stage_root_dir, if a do a backup from windows to unix via FTP?</b>

stage_root_dir=SAP/backup or

stage_root_dir=SAP\backup

Thank you very much

regards

[former_member207186]

Hi,

You may also check SAP Note
17163 - "BRARCHIVE/BRBACKUP messages and codes" (especially section "BR0328E").

Regards,
Bíborka

[Former Member]

hiii

I have same the problem, and solve to jhon sat command above,

SQL> alter tablespace PSAPSR3 end backup;

thank you jhon sat

[former_member1207545]

This solves my issue.

Regards

[Former Member]

for question 1

use tcode db02 then current size. in the layout check the last column "Backup" it should have NOT ACTIVE status

alternatively you can use

SQL> select status from v$backup;

[Former Member]

Hello!

Thank you very much for your response.

I have currently no access to the system.

Let's assume the status in Tcode DB02 is actvie or the SQL-command tells me the same, what should I do/check.

Can I execute "sqlplus / as sysdba"

ALTER TABLESPACE 1....., n END BACKUP

Does it some relation that my system is being used at the moment/what should I check?

Thank you very much

regards

[Former Member]

When u decided to check manually

connect to DB as sqlplus '/as sysdba'

This query displays which datafiles are currently included in a tablespace that has been placed in backup mode:

Sql> SELECT t.name AS "TB_NAME", d.file# as "DF#", d.name AS "DF_NAME", b.status FROM V$DATAFILE d, V$TABLESPACE t, V$BACKUP b

WHERE d.TS#=t.TS# AND b.FILE#=d.FILE# AND b.STATUS='ACTIVE';

SQL> ALTER TABLESPACE "TB_NAME" END BACKUP;

When tablespaces are in backup mode system can be used.

Vinod

[Former Member]

nothing to worry about the command

alter tablespace <ts> end backup;

if the tablespace is not in backup mode you can execute the same but will get error message which can be ignored.

[Former Member]

Hi ,

Are you taken backup successfully , if not pls check below things.

1,tablespace PSAPSR3 is already in backup status is caused last backup is not success.

pls check if any backup is running or not

ps -ef|grep brbackup .

2 , check any lock file is created under oracl/SID/sapbackup if s remove lock file from the directory .

3 , login into DB

> sqlplus /nolog

SQL*Plus: Release 10.2.0.4.0 - Production on Tue Oct 19 14:57:23 2010

Copyright (c) 1982, 2007, Oracle. All Rights Reserved.

SQL> connect /as sysdba

Connected.

SQL> select status from v$backup;

check the status it should not be ACTIVE .

from your case Tablespace PSAPSR3 is already in backup status so login into DB

> sqlplus /nolog

SQL*Plus: Release 10.2.0.4.0 - Production on Tue Oct 19 14:57:23 2010

Copyright (c) 1982, 2007, Oracle. All Rights Reserved.

SQL> connect /as sysdba

Connected.

alter tablespace PSAPSR3 end backup;

SQL> alter tablespace PSAPSR3 end backup;

Tablespace altered.

SQL> select status from v$backup;

STATUS

-

---

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

STATUS

-

---

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

STATUS

-

---

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

STATUS

-

---

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

NOT ACTIVE

41 rows selected.

SQL>

After complete the above activity pls fire the backup .

It might be resolve your issue .

[former_member209962]

thanks, old but usefull info

[Former Member]

this indicates that there was a problem with an earlier brbackup run.

check the logfiles and (if no backup is stil running) revert the backup status of the datafiles manually.

second question:

I would take the first one:

stage_root_dir=SAP/backup

the parameter refers the target directory which is of course on UNIX - therefore Unix notation.

peter