05-21-2008
Migrating Oracle from Big Endian to Little Endian Platorm
Hi,
We are trying to migrate an oracle database from Sun Solaris (SunOS 5.9 Generic_118558-28 sun4u sparc SUNW,Ultra-60) to Linux 2.6.18-53.1.19.el5 #1 SMP Tue Apr 22 03:01:10 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux which is basically a Big Endian to Little Endian conversion.
We shutdown the source database in Solaris and took a cold backup and placed the backup on the the Linux machine. We then converted each datafiles on Linux using the following RMAN commands.
convert datafile
'/d2/oradata/iol2005d/orig/bf2007q2.dbf'
,'/d2/oradata/iol2005d/orig/bf2007q4.dbf'
,'/d2/oradata/iol2005d/orig/system01.dbf'
....
.....
db_file_name_convert ('/d2/oradata/iol2005d/orig/','/d2/oradata/iol2005d/')
from platform 'Solaris[tm] OE (64-bit)';
parallelism = 3;
All the datafiles got converted sucessfully except the system datafile which errored out. Can we not convert the system datafile from Big Endian to Little Endian?
Thanks
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello,
Can anybody tell me whether the little endian-big endian issues will affect porting from True64 to HP UNIX or TCP/IP will take care of that? If it affects what can be the solution.
Thank you, (3 Replies)
Discussion started by: informshilpa
3 Replies
2. UNIX for Advanced & Expert Users
Hi all
I know AIX is big-endian machine.But does it read bytes in normal way from LSB.
Does it happen in some machine that at multi-byte integer level it is Little-endian and while reading a single byte it is Big-Endian.
This is urgent
Thanks in advance. (3 Replies)
Discussion started by: Shobhit
3 Replies
3. Programming
We are developing an application using TLI for network communication.The Server Code is developed in Sun and client in SCO unix. When we route data from Client to Server we encrypt the data using DES algotithm utility.The problem we are facing that Sun uses Big Endian methodology to store data in... (1 Reply)
Discussion started by: S.P.Prasad
1 Replies
4. UNIX for Advanced & Expert Users
Hi everybody,
I met this week a problem.
For now, we used TRU64 system based on alpha. Now, we're installing UP-UX systems (on Itanium). And we have problem with our files. Indeed, we use file with COMP-3, COMP-5 data. These files are used on both platforms. (we use also TXT files which... (1 Reply)
Discussion started by: bigmike59270
1 Replies
5. UNIX for Dummies Questions & Answers
Dear Friends,
I have one question in my mind. That question is
"how to detect whether the system is little endiean or big endian"
Processing the bit position is the difference between this endians.
But I could not understand how to find the pariticular sytem works... (3 Replies)
Discussion started by: Nirmal Babu
3 Replies
6. Solaris
hi folks, in the sparc v9 manul , it says it is possible to access the memory data in little-endian mode, but there is only privilaged instruction that could set the PSTATE ( the cle bit ) regist. if I'm in the user mode , is it possible for me to access the data in little-endian mode? (10 Replies)
Discussion started by: zerocool_08
10 Replies
7. UNIX and Linux Applications
Hi
Endian firewall free version if we do compare pfsense
For a LAN network with active user 1000
Which do you recommend
Share (0 Replies)
Discussion started by: mnnn
0 Replies
LEARN ABOUT DEBIAN
create_datafile_index
create_datafile_index(3alleg4) Allegro manual create_datafile_index(3alleg4)
NAME
create_datafile_index - Creates an index for a datafile. Allegro game programming library.
SYNOPSIS
#include <allegro.h>
DATAFILE_INDEX *create_datafile_index(const char *filename);
DESCRIPTION
Creates an index for a datafile, to speed up loading single objects out of it. This is mostly useful for big datafiles, which you don't
want to load as a whole. The index will store the offset of all objects inside the datafile, and then you can load it quickly with
"load_datafile_object_indexed" later. Use destroy_datafile_index to free the memory used by it again.
Note: If the datafile uses global compression, there is no performance gain from using an index, because seeking to the offset still
requires to uncompress the whole datafile up to that offset. Example:
DATAFILE_INDEX *index = create_datafile_index("huge.dat");
DATAFILE *object = load_datafile_object_indexed(index, 1234);
...
unload_datafile_object(object);
destroy_datafile_index(index);
RETURN VALUE
A pointer value which you can pass to load_datafile_object_indexed.
SEE ALSO
destroy_datafile_index(3alleg4), load_datafile_object_indexed(3alleg4)
Allegro version 4.4.2 create_datafile_index(3alleg4)