Or at least keep a complete oracle export on hand in case your final
plans fall through and you need to
play hero by recreating the old database.
Jeffrey Seger wrote:
Is this a business critical database? If so, I would go back to the
business and make an argument that the current database not
Maybe I'm missing something here, but isn't this simply a matter of
using DBD::CSV? You could open two dbi handles, one to your existing
Oracle db and the other to a csv db. Read from the one, write to the
other. When you get the new schema set up on the new platform, do the
same thing in the re
I’m having a problem with a DBI script on our Solaris systems. The scripts run
fine on my Linux workstation. The script will return the correct data and then
displays the error. I have found many places discussing this error, but none of
them has a solution. If you need more information about
Hi Curtis
> export to CSV and use DBD::CSV?
Or, as a last resort, use Perl :-)
http://search.cpan.org/~rsavage/DBIx-Admin-BackupRestore-1.10/
--
Ron Savage
[EMAIL PROTECTED]
http://savage.net.au/index.html
Very well put, Jeffrey. That was exactly the thought bothering me after
I posted my reply. Is it really written in stone that the original
database will be destroyed after their one attempt at making a backup?
Such a decision would be highly suspect. Surely they could find one
spare PC to keep
On Thu, Jun 19, 2008 at 1:53 PM, Tim Bunce <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 18, 2008 at 02:14:06PM -0700, Douglas Wilson wrote:
>> With RaiseError or PrintError set, if DBD::Sybase throws an error, the
>> error message does not indicate what line number of the program that the
>> error was
Is this a business critical database? If so, I would go back to the
business and make an argument that the current database not be allowed to go
away till the new database is in place, migrated and tested. Regardless of
the tool you use to migrate it, you will run the risk of data loss if the
old
On Wed, Jun 18, 2008 at 02:14:06PM -0700, Douglas Wilson wrote:
> With RaiseError or PrintError set, if DBD::Sybase throws an error, the
> error message does not indicate what line number of the program that the
> error was on ... or what program/module that the error was in.
I'd guess that that's
On Thu, Jun 19, 2008 at 11:54 AM, Curtis Leach <[EMAIL PROTECTED]> wrote:
> My big problem is that the new database hasn't been selected yet & the
> our only Oracle database will be gone by the time one is selected.
> Which was the reason for the need of a database independent solution. I
> won't
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> My big problem is that the new database hasn't been selected yet & the
> our only Oracle database will be gone by the time one is selected.
> Which was the reason for the need of a database independent solution. I
> won't be able to load it b
Curtis Leach wrote:
My big problem is that the new database hasn't been selected yet & the
our only Oracle database will be gone by the time one is selected.
Which was the reason for the need of a database independent solution. I
won't be able to load it back into Oracle again for a 2nd attempt.
export to CSV and use DBD::CSV?
Curtis Leach wrote:
My big problem is that the new database hasn't been selected yet & the
our only Oracle database will be gone by the time one is selected.
Which was the reason for the need of a database independent solution. I
won't be able to load it back int
My big problem is that the new database hasn't been selected yet & the
our only Oracle database will be gone by the time one is selected.
Which was the reason for the need of a database independent solution. I
won't be able to load it back into Oracle again for a 2nd attempt.
Curtis
-Origina
I guess I'd be more concerned initially with ensuring the datatype
mappings are identical or in the 'to-be' database, the ingress is valid.
Has that been considered yet?
On Thu, 19 Jun 2008, Curtis Leach wrote:
Does anyone know of a module that would backup an Oracle database in a
database in
Does anyone know of a module that would backup an Oracle database in a
database independent way?
We are decommissioning our only Oracle database & we would like to be
able to preserve it's contents so that it can be reloaded into another
database at a later date. Such as Windows SQL Server or Inf
With RaiseError or PrintError set, if DBD::Sybase throws an error, the
error message does not indicate what line number of the program that the
error was on ... or what program/module that the error was in.
DBD::Oracle and DBD::ODBC both have program/module line numbers at the
end of the error mes
Me thinks your Perl was compiled using one flavour of C compiler and you
are trying to compile DBD::Oracle with another flavour or C compiler.
I have seen this a number of times with HP systems.
Basically it meas you have to recompile your Perl with the same C
compiler you are going to use to
Thanks for the response John.
I just tried the same thing on perl 5.10 and had the same results.
Perl Makefile.PL and make output shown below.
Perl Makefile.PL looks ok to me - but I am far from expert,
clearly!!
I can see a problem with the includes in the make output but
To start you should post the output of your perl Makefil.PL as that
will give the other here on the list a good deal of what we need to go on.
Also you should have a look at the readmes they might help
Cheers John Scoles
Stewart Anderson wrote:
Hi,
I'm having real probs getting DBD::Orac
Hi,
I'm having real probs getting DBD::Oracle onto a sphinx version of
MAC OS ppc.
I have tried numerous repositories but can't find pre-compiled modules.
If they exist somewhere please can you point me in the right direction.
I have also tried to complie the module myself but am gettin
20 matches
Mail list logo
