-
The datafiles might have the sae block size problem.
-
what do u mean by endian? is it the same as indian
-
Originally Posted by yxez
what do u mean by endian? is it the same as indian
It is Datafile byte ordering - OS feature.
Code:
SQL> select * from v$transportable_platform ;
PLATFORM_ID PLATFORM_NAME ENDIAN_FORMAT
----------- ---------------------------------------- --------------
1 Solaris[tm] OE (32-bit) Big
2 Solaris[tm] OE (64-bit) Big
7 Microsoft Windows IA (32-bit) Little
10 Linux IA (32-bit) Little
6 AIX-Based Systems (64-bit) Big
3 HP-UX (64-bit) Big
5 HP Tru64 UNIX Little
4 HP-UX IA (64-bit) Big
11 Linux IA (64-bit) Little
15 HP Open VMS Little
8 Microsoft Windows IA (64-bit) Little
PLATFORM_ID PLATFORM_NAME ENDIAN_FORMAT
----------- ---------------------------------------- --------------
9 IBM zSeries Based Linux Big
13 Linux 64-bit for AMD Little
16 Apple Mac OS Big
12 Microsoft Windows 64-bit for AMD Little
15 rows selected.
If the OS is developed in in India... then May be it can be indian..
-
Originally Posted by yxez
what do u mean by endian? is it the same as indian
have you heard of google?
-
Originally Posted by pando
cant you restore the backup and open with resetlogs?
may be redo log would be created with 512 bytes block size
I tried that, however the system datafile needed recovery which it was not able to perform since it required the redo log and couldn't read it.
-
Originally Posted by jhmartin
The datafiles might have the sae block size problem.
The datafiles would not have the issue. Since typically they are set by the pfile parameter block_size and since the advent of multiple block sizes in the db this is most likely a dynamically determined item since it is stored in the file header of each data file.
However, there might be differences in block layout based upon the Platform.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|