ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 237

Hello,
I encountered ORA-10561 while I was recovering my DB.
Problem Background :-
I took a hotbakup of my DB running in Windows, I edited the Pfile and recreated the control file
I was able to succesfully mount the DB
The I gave the below command to apply the redologs and recover the DB
And the errors followed as mentioned.
The HOTBACKUP was copied and restored using a USB-PENdrive. I suspect that the datafiles and / or ARCHIVE LOGS would have had some format issues due to O/S {WINXP ---> RHEL5}
If this is the case ? then I would like to know how to convert the format of the files(Datafiles and or Redologs)
into acceptable format
>
SQL> recover database until time '2010-03-15:18:08:05' using backup controlfile;
ORA-00279: change 3447582 generated at 03/15/2010 17:41:42 needed for thread 1
ORA-00289: suggestion : /home/oracle/NEW/ARCHIVE/ARC0000000144_0706577643.0001
ORA-00280: change 3447582 for thread 1 is in sequence #144
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/home/oracle/NEW/ARCHIVE/ARC00144_0706577643.001
ORA-00283: recovery session canceled due to errors
ORA-10562: Error occurred while applying redo to data block (file# 1, block#
1658)
ORA-10564: tablespace SYSTEM
ORA-01110: data file 1: '/home/oracle/NEW/oradata/O1_MF_SYSTEM_5M9ZKSSW_.DBF'
ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 237
ORA-00600: internal error code, arguments: [4502], [0], [], [], [], [], [], []
>
Thanks in advance.
Regards,
Valli

You need to give much more information:
What version of Oracle? 10gR2 is not a version, 10.2.0.1 is a version.
What version of Windows, exactly? What version of linux?
ORA-600 means you need to talk to Oracle support. There is an ora-600 lookup tool, which basically searches the knowledge base (for ora-600[4502] in your case, which brings up a bunch of really, really, really old docs).
How exactly did you take the "hot backup?" There are a number of ways to do things with that name, some of which are just plain wrong.
How exactly did you get the backup from one machine to another? Which exact commands did you use to copy the files to the usb and from the usb? Did you do it more than once?
Why are you using the backup controlfile syntax? There are valid reasons, and invalid reasons to do that.
What exactly did you change in the pfile?
What does the alert log say about all this?

Similar Messages

Data: stru_tab type ref to data? what data refers to?

Dear friends,
                     Relatively iam new to WDA. can u please explain me below statement.
data: stru_tab type ref to data.

Actually there are not really any Web Dynpro sepecific data types. The ones mentioned are simply data dictionary data types that are defined for use with WD, but can be used in any ABAP applications. You should start your research with just ABAP data types. Look in the ABAPDOCU transaction or search the keyword documentation for DATA. There is lots of documentation on the ABAP native data types.
Here is a little bit of it:
Predefined ABAP Types
The table below shows the predefined ABAP types. Additional attributes can be found under value ranges and initial values.
Type Length Standard length Description
b 1 Byte   1 byte integer (internal)
c 1 to 65,535 characters 1 character Text field
cursor as i as i Database cursor
d 8 characters   Date field
f 8 bytes   Floating point number
i 4 bytes   4 byte integer
n 1 to 65,535 characters 1 character Numeric text
p 1 to 16 bytes 8 bytes Packed number
string variable   Text string
s 2 bytes   2 byte integer (internal)
t 6 characters   Time field
x 1 to 65,535 bytes 1 byte Byte field
xstring variable   Byte string
These types are predefined in every ABAP program.
All predefined ABAP types in this table are elementary.
Apart from the types b and s, the predefined ABAP types can also be used to define your own data types and data objects and for typing. The types b and s cannot be specified directly in ABAP statements. Self-defined data types and data objects in ABAP programs are of the data type b and s if they are defined with reference to data elements to the ABAP Dictionary which are of the external data types INT1 or INT2.
The predefined data types string and xstring describe data objects of variable length (dynamic data objects). While the length of data objects in all other elementary data types is determined for its whole lifetime, the length of text and byte strings varies according to their content (the maximum size of a string is determined by profile parameter ztta/max_memreq_MB, see Maximum size of dynamic data objects).
The program-globally predefined data type cursor is currently synonymous with the predefined ABAP type i. This is required for the declaration of a cursor variable for database cursor handling.
All predefined ABAP types for which a length interval is specified in second column in the table are generic, which means that the length is not part of the type description. For the type p, the fractional portion is indefinite as well as the length.
The entries in the standard length column specify the length that is used for the corresponding generic data type when declaring data objects, if no explicit length is specified in the relevant statement.
In Unicode systems, the length must either be specified in characters and bytes. In non-Unicode systems, the length of a character is one byte, but in Unicode systems the length of a character depends on which Unicode character representation is used.
Generic ABAP Types
The following table shows the predefined generic ABAP types. A generic data type is an incomplete type specification that includes several complete type specifications. The generic types can be used for the typing of field symbols and formal parameters. The only generic type that can be used for typing of data references is the predefined type data. The predefined generic type for object references is object. When a data object is assigned to generically typed field symbols using the statement ASSIGN, or to a formal parameter in procedure calls, the system checks whether its concrete data type is a of the generic type, or is compatible with it.
Type Description
any Any data type (suitable for any type)
any table Internal table of any table type
c Text field of generic length
clike Character-type (c, d, n, t, string and character-type flat structures); in non- Unicode programs also x, xstring and any flat structures
csequence Text-type (c, string)
data Any data type
hashed table Hashed table
index table Index table
n numeric text of generic length
numeric Numeric (b, i, p, f, s)
object Any object type (root class of the inheritance hierarchy)
p Packed number of generic length and generic number of decimal places
simple Elementary data type including structured types with exclusively character-type flat components
sorted table Sorted table
Standard table Standard table
table Standard table
x Byte field of generic length
xsequence byte-type (x, xstring)
The genric types clike, csequence, numeric,simple, and xsequence are available as of release 6.10.
Notes
The generic type any currently has the same effect in typing as the generic type data. When declaring references, any cannot yest be specified after REF TO. Generic data references (REF TO data) or generic object references (REF TO object) are possible. The generic type object can currently only be specified after REF TO.
Except for the built-in generic types illustrated in the table above, there are at the moment no self-defined generic types in ABAP with only one exception: A table type defined with TYPES - TABLE OF or defined in the ABAP Dictionary without completely specifying the table key, is also generic.
Predefined Types in the ABAP Dictionary
The following table lists the predefined types in the ABAP Dictionary. These types cannot be used directly in ABAP programs, and are therefore known as external data types. Instead, they are used in the ABAP Dictionary for the definition of data types to which ABAP programs can refer. The predefined data types of the ABAP Dictionary must also be taken into account in Open SQL statements and when working with screens: Open SQL statements work with database tables defined in the ABAP Dictionary whose colums have external data types. Screen fields are also declared in the Screen Painter with reference to external data types.
Type Permitted Places m Meaning ABAP Type
ACCP 6 Accounting period n(6)
CHAR 1-255 Character string c(m)
CLNT 3 Client c(3)
CUKY 5 Currency key c(5)
CURR 1-31 Currency field p((m+1)/2)
DATS 8 Date d
DEC 1-31 Calculation/amount field p((m+1)/2)
FLTP 16 Floating point number f(8)
INT1 3 1 byte integer b
INT2 5 2 byte integer s
INT4 10 4 byte integer i
LANG 1 Language c(1)
LCHR 256-... Long character string c(m)
LRAW 256-... Long byte string x(m)
NUMC 1-255 numerischer Text n(m)
PREC 2 Accuracy of a quantity field s
QUAN 1-31 Quantity field p((m+1)/2)
RAW 1-255 Byte sequence x(m)
RAWSTRING 256-... Byte sequence xstring
SSTRING 1-255 Character string string
STRING 256-... Character string string
TIMS 6 Time t
UNIT 2-3 Unit key c(m)
For types LCHR and LRAW, the maximum number of places in a transparent database table is the value of the preceding INT2 field.
The types RAWSTRING and STRING have a variable length. A maximum length for these types can be specified, but has no upper limit.
The type SSTRING is available as of release 6.10 and it has a variable length. Its maximum length must be specified and is limited to 255. The advantage of this type compared with CHAR, is that it is assigned to the ABAP type string.
The table below shows the data types of the ABAP Dictionary that are based on the predefined types in the above table, and that can be addressed in an ABAP program. The elementary components of these data types are converted to predefined ABAP data types according to the final column in the above table, whereby the number of places m of each type is converted to lengths.
Data types in the ABAP Dictionary Data types in ABAP
Data element Elementary data type, Reference type
Structure, Database table, View Structured data type
Table type Table type
Note
As of release 6.20, a component of structures or database tables that has the type LANG can be identified as a text language. The text language is used for the conversion of character-type components of the structure when importing data from data clusters and for RFC between MDMP systems and Unicode systems.

Difference b/w DATA TYPE and DATA OBJECT & differences b/w TYPE and LIKE

hai
can any one say the differences between Data type and Data Object.
And also differences between TYPE and LIKE
thanks
Gani

hi,
_Data Types and Data Objects_
      Programs work with local program data that is, with byte sequences in the working memory. Byte sequences that belong together are called fields and are characterized by a length, an identity (name), and as a further attribute by a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
      In the ABAP type concept, fields are called data objects. Each data object is thus an instance of an abstract data type. There are separate name spaces for data objects and data types. This means that a name can be the name of a data object as well as the name of a data type simultaneously.
Data Types
   As well as occurring as attributes of a data object, data types can also be defined independently. You can then use them later on in conjunction with a data object. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
     All programming languages distinguish between various types of data with various uses, such as .. type data for storing or displaying values and numerical data for calculations. The attributes in question are described using data types. You can define, for example, how data is stored in the repository, and how the ABAP statements work with the data.
Data types can be divided into elementary, reference, and complex types.
a. Elementary Types
These are data types of fixed or variable length that are not made up of other types.
The difference between variable length data types and fixed length data types is that the length and the memory space required by data objects of variable length data types can change dynamically during runtime, and that these data types cannot be defined irreversibly while the data object is being declared.
Predefined and User-Defined Elementary Data Types
You can also define your own elementary data types in ABAP using the TYPES statement. You base these on the predefined data types. This determines all of the technical attributes of the new data type. For example, you could define a data type P_2 with two decimal places, based on the predefined data type P. You could then use this new type in your data declarations.
b. Reference Types
Reference types are deep data types that describe reference variables, that is, data objects that contain references. A reference variable can be defined as a component of a complex data object such as a structure or internal table as well as a single field.
c. Complex Data Types
Complex data types are made up of other data types. A distinction is made here between structured types and table types.
Data Objects
      Data objects are the physical units with which ABAP statements work at runtime. The contents of a data object occupy memory space in the program. ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type.. For example, statements can write the contents of data objects in lists or in the database, they can pass them to and receive them from routines, they can change them by assigning new values, and they can compare them in logical expressions.
       Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running (field length, number of decimal places, and data type). You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
        A data object is a part of the repository whose content can be addressed and interpreted by the program. All data objects must be declared in the ABAP program and are not persistent, meaning that they only exist while the program is being executed. Before you can process persistent data (such as data from a database table or from a sequential file), you must read it into data objects first. Conversely, if you want to retain the contents of a data object beyond the end of the program, you must save it in a persistent form.
Declaring Data Objects
      Apart from the interface parameters of procedures, you declare all of the data objects in an ABAP program or procedure in its declaration part. These declarative statements establish the data type of the object, along with any missing technical attributes. This takes place before the program is actually executed. The technical attributes can then be queried while the program is running.
     The interface parameters of procedures are generated as local data objects, but only when the procedure is actually called. You can define the technical attributes of the interface parameters in the procedure itself. If you do not, they adopt the attributes of the parameters from which they receive their values.
ABAP contains the following kinds of data objects:
a. Literals
Literals are not created by declarative statements. Instead, they exist in the program source code. Like all data objects, they have fixed technical attributes (field length, number of decimal places, data type), but no name. They are therefore referred to as unnamed data objects.
b. Named Data Objects
Data objects that have a name that you can use to address the ABAP program are known as named objects. These can be objects of various types, including text symbols, variables and constants.
Text symbols are pointers to texts in the text pool of the ABAP program. When the program starts, the corresponding data objects are generated from the texts stored in the text pool. They can be addressed using the name of the text symbol.
Variables are data objects whose contents can be changed using ABAP statements. You declare variables using the DATA, CLASS-DATA, STATICS, PARAMETERS, SELECT-OPTIONS, and RANGESstatements.
Constants are data objects whose contents cannot be changed. You declare constants using the CONSTANTSstatement.
c. Anonymous Data Objects
Data objects that cannot be addressed using a name are known as anonymous data objects. They are created using the CREATE DATAstatement and can be addressed using reference variables.
d. System-Defined Data Objects
System-defined data objects do not have to be declared explicitly - they are always available at runtime.
e. Interface Work Areas
Interface work areas are special variables that serve as interfaces between programs, screens, and logical databases. You declare interface work areas using the TABLES and NODESstatements.
What is the difference between Type and Like?
Answer1:
TYPE, you assign datatype directly to the data object while declaring.
LIKE,you assign the datatype of another object to the declaring data object. The datatype is referenced indirectly.
Answer2:
Type is a keyword used to refer to a data type whereas Like is a keyword used to copy the existing properties of already existing data object.
Answer3:
type refers the existing data type
like refers the existing data object
reward if useful
thanks and regards
suma sailaja pvn

Data types and Data object

Can Any one give me Clear definition of Data type and Data objects.
Concept i know clearly.. but unable to explain it..
Regards,
Prasanna

Data consists of strings of bytes in the memory area of the program. A string of related bytes is called a field. Each field has an identity (a name) and a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
 In the ABAP type concept, fields are called data objects. Each data object is an instance of an abstract data type. Data types in ABAP are not just attributes of fields, but can be defined in their own right. There are separate name spaces for data objects and data types. This means that a name can at the same time be the name of a data object as well as the name of a data type.
Data Types:
 As well as occurring as attributes of a data object, data types can also be defined independently. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program (using the TYPES statement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
 Data types can be divided into elementary, reference, and complex types
Data objects:
 Data objects are the physical units with which ABAP statements work at runtime. Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running. The technical attributes of a data object are its length, number of decimal places, and data type. ABAP statements work with the contents of data objects and interpret them according to their data type. You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
ABAP contains the following kinds of data objects
Literals
 Named Data Objects
Predefined Data Objects
Dynamic Data Objects

Data types and data objects

diff b/w data types and data objects

hi prasanth,
Data Types and Data Objects
Programs work with local program data that is, with byte sequences in the working memory. Byte sequences that belong together are called fields and are characterized by a length, an identity (name), and as a further attribute by a data type. All programming languages have a concept that describes how the contents of a field are interpreted according to the data type.
In the ABAP type concept, fields are called data objects. Each data object is thus an instance of an abstract data type. There are separate name spaces for data objects and data types. This means that a name can be the name of a data object as well as the name of a data type simultaneously.
Data Types
Data types are templates for creating data objects. Data types can be defined independently in the ABAP program or in the ABAP Dictionary. As attributes of a data object, data types can also exist in a non-independent state. Data types do not use any memory space for work data, but may require memory for administration information.
As well as occurring as attributes of a data object, data types can also be defined independently. You can then use them later on in conjunction with a data object. The definition of a user-defined data type is based on a set of predefined elementary data types. You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary. You can use your own data types to declare data objects or to check the types of parameters in generic operations.
All programming languages distinguish between various types of data with various uses, such as .. type data for storing or displaying values and numerical data for calculations. The attributes in question are described using data types. You can define, for example, how data is stored in the repository, and how the ABAP statements work with the data.
Data types can be divided into elementary, reference, and complex types.
a. Elementary Types
These are data types of fixed or variable length that are not made up of other types.
The difference between variable length data types and fixed length data types is that the length and the memory space required by data objects of variable length data types can change dynamically during runtime, and that these data types cannot be defined irreversibly while the data object is being declared.
Predefined and User-Defined Elementary Data Types
You can also define your own elementary data types in ABAP using the TYPES statement. You base these on the predefined data types. This determines all of the technical attributes of the new data type. For example, you could define a data type P_2 with two decimal places, based on the predefined data type P. You could then use this new type in your data declarations.
b. Reference Types
Reference types are deep data types that describe reference variables, that is, data objects that contain references. A reference variable can be defined as a component of a complex data object such as a structure or internal table as well as a single field.
c. Complex Data Types
Complex data types are made up of other data types. A distinction is made here between structured types and table types.
Data Objects
A data object is an instance of a data type and occupies as much memory space as its type specifies. An ABAP program only works with data that is available as content of data objects. Data objects are either created implicitly as named data objects, or exanonymous data objects using CREATEDATA.
Data objects are the physical units with which ABAP statements work at runtime. The contents of a data object occupy memory space in the program. ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type.. For example, statements can write the contents of data objects in lists or in the database, they can pass them to and receive them from routines, they can change them by assigning new values, and they can compare them in logical expressions.
Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running (field length, number of decimal places, and data type). You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures). As well as fields in the memory area of the program, the program also treats literals like data objects.
A data object is a part of the repository whose content can be addressed and interpreted by the program. All data objects must be declared in the ABAP program and are not persistent, meaning that they only exist while the program is being executed. Before you can process persistent data (such as data from a database table or from a sequential file), you must read it into data objects first. Conversely, if you want to retain the contents of a data object beyond the end of the program, you must save it in a persistent form.
Declaring Data Objects
Apart from the interface parameters of procedures, you declare all of the data objects in an ABAP program or procedure in its declaration part. These declarative statements establish the data type of the object, along with any missing technical attributes. This takes place before the program is actually executed. The technical attributes can then be queried while the program is running.
The interface parameters of procedures are generated as local data objects, but only when the procedure is actually called. You can define the technical attributes of the interface parameters in the procedure itself. If you do not, they adopt the attributes of the parameters from which they receive their values.
ABAP contains the following kinds of data objects:
a. Literals
Literals are not created by declarative statements. Instead, they exist in the program source code. Like all data objects, they have fixed technical attributes (field length, number of decimal places, data type), but no name. They are therefore referred to as unnamed data objects.
b. Named Data Objects
Data objects that have a name that you can use to address the ABAP program are known as named objects. These can be objects of various types, including text symbols, variables and constants.
Text symbols are pointers to texts in the text pool of the ABAP program. When the program starts, the corresponding data objects are generated from the texts stored in the text pool. They can be addressed using the name of the text symbol.
Variables are data objects whose contents can be changed using ABAP statements. You declare variables using the DATA, CLASS-DATA, STATICS, PARAMETERS, SELECT-OPTIONS, and RANGESstatements.
Constants are data objects whose contents cannot be changed. You declare constants using the CONSTANTSstatement.
c. Anonymous Data Objects
Data objects that cannot be addressed using a name are known as anonymous data objects. They are created using the CREATE DATAstatement and can be addressed using reference variables.
d. System-Defined Data Objects
System-defined data objects do not have to be declared explicitly - they are always available at runtime.
e. Interface Work Areas
Interface work areas are special variables that serve as interfaces between programs, screens, and logical databases. You declare interface work areas using the TABLES and NODESstatements.
regards,
sravanthi

Use an imported RFC's type as type in the custom data object

Hello,
I've imported an RFC function in my process. There were created automatically some RFC types describing RFC's input\output parameters. Now I want to create my custom data object type and want to use previously created type in my data object, but I can use only standard types like string or anyType. There aren't any of generated types in the list.
Is it possible to use generated types as types in a custom data object?

Hi,
Where did you import the RFC? In WebDynpro application? If so, you need to expose the types through the Interface Controller then only the types will be visible in BPM process.
Thanks
Abhilash

Difference Between Data Type and Data Object

Difference Between Data Type and Data Object

hi magesh
Data types can be divided into
elementary,
reference, and
complex types.
Elementary Types
Elementary types are the smallest indivisible unit of types. They can be grouped as those with fixed length and those with variable length.
Fixed-Length Elementary Types
There are eight predefined types in ABAP with fixed length:
Four character types:
Character (C),
Numeric character (N),
Date (D),
and Time (T).
One hexadecimal type:
Byte field (X).
Three numeric types:
Integer (I),
Floating-point number (F)
and Packed number (P).
Variable-Length Elementary Types
There are two predefined types in ABAP with variable length:
STRING for character strings
XSTRING for byte strings
Reference Types
Reference types
describe data objects that contain references (pointers) to other objects (data objects and objects in ABAP Objects).
Data Types
1) As well as occurring as attributes of a data object, data types can also be defined independently.
2)You can then use them later on in conjunction with a data object.
3) The definition of a user-defined data type is based on a set of predefined elementary data types.
4) You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary.
5) You can use your own data types to declare data objects or to check the types of parameters in generic operations.
Data Objects
1)Data objects are the physical units with which ABAP statements work at runtime.
2) The contents of a data object occupy memory space in the program.
3) ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type..
4) For example, statements can write the contents of data objects in lists or in the database, they can pass them to and receive them from routines, they can change them by assigning new values, and they can compare them in logical expressions.
5) Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running (field length, number of decimal places, and data type).
6) You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures).
7) As well as fields in the memory area of the program, the program also treats literals like data objects.
hope this helps u,
reward points if useful
Ginni

How to organize Data Objects and other Objects in SWCV

Hi,
I am looking for Best Practices on how to organize data objects in SWCV as well as other objects such as a Distribution Rules.
We are planning to develop three occasionally connected applications with NW Mobile 7.1 this year and maybe additional one the following year. We will create multiple Standard Data Objects (e.g. Plant, Company Code, Reservations, ...) which are shared in the first set of transactions and in the future transactions.
I have heard before to separate out Standard Data Objects from Distribution Models and have two different SWCV.
Should I have a) one SWCV for all current and future Standard Data Objects and one for the distribution rtules or b) should I separate out common data objects into one SWCV, and all transaction-specific data object each into separate SWCV?
Just wondering if there are any best practices available for this so that I won't run into problems in the future when we want to add more transactions/data objects?
Any advise is appreciated.
Thanks,
W. Berger

Hi Siva,
Thanks for quick reply!!
I have created say SWCV1 for Dataobjects.
Now i want to create seperate SWCV2 for defining distribution model.
How i should proceed..I cannot see the uses option while creating new SWCV2 ( Only option i see is 'backward compatibility checkbox : uses NW04/NW04s MI Application')
where to check the following which you have mentioned?
SWCV2 was created and inherited SWCV1 in uses tab of SWCV2.
Thanks in advance!!
Regards
Devendra

ORA -10567 : Redo is inconsistent with data block...

Hi All !!
Two days back I installed oracle 10g on windows XP and today my database is giving problem as it's in mount state and not opening for normal operation.
When I give command 'alter database open' then it's giving error ORA-10567 : Redo is inconsistent with data block...I have no earlier backup for database
and also no backup for any datafile. I crosschecked the status of datafile and found that there are block corruption in datafile 2 & 4 (users and undotbs01)..I used blockrecover coomand too for block corruption but not able to correct those blocks..plz suggest me that how can I fix this error ORA-10567.
Thanks
With Best Regards
-avichal

Hi Ramesh,
I reckon you should try these out:
- identify the tablespace that file belongs to in the production db.
- put the that tablespace in backup mode on the prod db
- shutdown your standby database
- overwrite the problematic datafile with the corresponding datafile from production database
- put the tablespace above in end backup mode
- startup your standby database and issue the recover command.
Well, there you go. Your standby database should be all fine now.
Regards
Pranilesh Chand

Block CIF differentiating data objects

Hello,
Following one of SAP recommendation, we are blocking the Inbound CIF Queues every time we run the SNP Optimizer in the active version. To do this, we are using the report /SAPAPO/CIFSTOPQUEUES. In this report it is necessary to use a Queue Name to be able to stop the queues and the RFC destination of APO in R/3.
The issue that we are trying to solve is we need to find a way to differentiate the data objects by their content, instead of blocking every CF*, because we donu2019t want to block the CIF Queues for all the Business Units implemented in the same APO Client.
For example, we need that the CIF Queues of the Business Unit A could be differentiated from the CIF Queues of the Business Unit B, so at the moment of blocking them we could use the differentiated queue name, affecting just the Business Unit related.
Kind Regards.

Hi ,
Unfortunately you can only block the transfer of transactional data at global level.There is no badi or exit available to change the name of CIF queue as they are system generated.So the scenario which you are trying to achieve to diiferentiate at business unit level by CIF queues is not feasible.
You can achieve it by dividing your planning run in batch mode (seperate planning run for different business unit selections) and strictly following the timings during whcih each BU users will be directed the time during which they can not do changes.While rest BU can do as you are sure that thier objects are not taken in the current planning run.
Instead of CF* queue blocks , you can go one step below by stopping the specific order type queues like CFSLS* (SO) , CIFPO(Purchase req and order) ,CIFSTK (stocks).
You can refer to the note 1228423 which clearly mentions the shortfalls of parallel APO planning run and online transfer.
So better to run the planning run operations at night :)..when load is less.
Regards,
Nikhil Nalgirkar

Management Portal unavailable - "cannot load management data for this resource type"

Noticing that with the exception of virtual machines, every resource type in the (non preview) Azure Management Portal is showing a sad pink icon and the help text "cannot load management data for this resource type."
So that's a near total portal outage for us. Anybody else experiencing this?
I've attempted to open a ticket with developer support but I'm not sure if that's the right channel.
Brian

Hi Brian,
Thanks for your posting!
From Dashboard shown (http://azure.microsoft.com/en-us/status/#history), Currently, the Azure portal works fine in every regions.
So I suggest you can submit a tick via this channel:
http://www.windowsazure.com/en-us/support/contact/
Also, you can click your right-top account name and select the "Microsoft Support" item to create free ticket.
Regards,
Will
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.

ORA-19599: block number 1985 is corrupt in archived log +FG/

Hi Team,
I couldn't take backup of the RAC database archivelog. Please help me
RMAN> BACKUP VALIDATE DATABASE ARCHIVELOG ALL;
Starting backup at 24-MAR-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=+DG1/kvxcprd/datafile/system.260.777756857
input datafile fno=00003 name=+DG1/kvxcprd/datafile/sysaux.268.777756857
input datafile fno=00002 name=+DG1/kvxcprd/datafile/undotbs1.263.777756857
input datafile fno=00005 name=+DG1/kvxcprd/datafile/undotbs2.264.777756983
input datafile fno=00004 name=+DG1/kvxcprd/datafile/users.267.777756857
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:25
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=2 sequence=17 recid=26 stamp=810915691
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/24/2013 14:37:11
ORA-19599: block number 1985 is corrupt in archived log +FG/kvxcprd/archivelog/2013_03_24/thread_2_seq_17.269.810915689
RMAN> backup archivelog all;
Starting backup at 24-MAR-13
current log archived
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 03/24/2013 14:39:52
ORA-19563: header validation failed for file
Thanks & Regards,
Edited by: 995796 on Mar 24, 2013 2:26 AM
Edited by: 995796 on Mar 24, 2013 2:27 AM

RMAN> BACKUP VALIDATE DATABASE ARCHIVELOG ALL;
Starting backup at 24-MAR-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=+DG1/kvxcprd/datafile/system.260.777756857
input datafile fno=00003 name=+DG1/kvxcprd/datafile/sysaux.268.777756857
input datafile fno=00002 name=+DG1/kvxcprd/datafile/undotbs1.263.777756857
input datafile fno=00005 name=+DG1/kvxcprd/datafile/undotbs2.264.777756983
input datafile fno=00004 name=+DG1/kvxcprd/datafile/users.267.777756857
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:25
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=2 sequence=17 recid=26 stamp=810915691
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/24/2013 14:37:11
ORA-19599: block number 1985 is corrupt in archived log +FG/kvxcprd/archivelog/2013_03_24/thread_2_seq_17.269.810915689You can remove this log with command
rman> delete archivelog '+FG/kvxcprd/archivelog/2013_03_24/thread_2_seq_17.269.810915689';

AR TRANSACTIONS 화면에서 TRANSACTION TYPE LOV에 SEEDED DATA가 나오지않을경우

제품 : FIN_AR
작성날짜 : 2003-05-22
AR TRANSACTIONS 화면에서 TRANSACTION TYPE LOV에 SEEDED DATA가 나오지않을경우
===============================================================
PURPOSE
AR TRANSACTIONS 화면에서 TRANSACTION TYPE LOV에 SEEDED DATA가 나오지않을경우
Problem Description
AR TRANSACTIONS 화면에서 TRANSACTION TYPE LOV에 SEEDED DATA가 나오지않을경우는 RA_CUST_TRX_TYPES_ALL의 set_of_book_id값이 NULL이여서 생긴 문제이다.
Workaround
Solution Description
System Administrator권한으로 concurrent program"replicate seed data"를
각 org별로 실행하면 해결된다.
그래도 해결되지않을 경우에는 오라클 RC로 문의하길 바랍니다.
Reference Documents
Note:124182.1

LabVIEW MilliSecs support manager function and Tick Count block diagram object

Is the output of the support manager function MilliSecs (used in a CIN) directly comparable with the time returned by the Tick Count (ms) block diagram object? i.e. if they have the same value then it is the 'same' time allowing for OS specific time resolution

> Is the output of the support manager function MilliSecs (used in a
> CIN) directly comparable with the time returned by the Tick Count (ms)
> block diagram object? i.e. if they have the same value then it is the
> 'same' time allowing for OS specific time resolution
The LV diagram node is built upon the MilliSecs() function, which is
built upon various OS specific functions. It is safe to treat them as
though they are the same function and represent the same clock.
Greg McKaskle

"No management data available" message in SARA transaction

Hi,
I am trying for CRM data Archiving. After scheduling a job by "Write" button, when i click on "Management" button, it gives me a message "
No management data available"
I want to know why is this showing and is there is any configuration missing for this.
Regards,
Preetesh

Hi Christophe,
Thanks for your reply.
In CRM_JEST table there are records which have status as "Can be archived" (I1100).
Also when i schedule the job from SARA, it gets started then finished, but no spool list gets generated.
I have activated the info structure also but no data is displayed.
Plz let me know if I am missing any configutation.
Regards,
Preetesh.

ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 237

Similar Messages

Maybe you are looking for