Worldwide
Managed Services for
OpenVMS and Rdb
About
Software
Concepts
International
LLC
About
Software
Concepts
International,
LLC
Questions
to
Consider
How
to
Upgrade
to
Rdb
V7 2
How
to
Upgrade
to
Rdb
V7.2
Moving
Your
Data
Validating
the
Mo ed
Data
Validating
the
Moved
Data
Cutting
Over
to
New
System
Q
i
d
F db k
About
Software
Concepts
International
About
Software
Concepts
International…
The
leading
provider
of
managed
services
for
Rdb
DBMS
and
OpenVMS
for
Rdb,
DBMS
and
OpenVMS
24+
years
in
the
business
Performed
many
many
many
successful
Rdb
Performed
many,
many,
many
successful
Rdb,
DBMS
and
OpenVMS
migrations
from
VAX
Æ
Alpha
VAX
Æ
Integrity and
VAX
Æ
Alpha,
VAX
Æ
Integrity and
About
Software
Concepts
International
LLC
About
Software
Concepts
International,
LLC
Questions
to
Consider
How
to
Upgrade
to
Rdb
V7 2
How
to
Upgrade
to
Rdb
V7.2
Moving
Your
Data
Validating
the
Mo ed
Data
Validating
the
Moved
Data
Cutting
Over
to
New
System
Q
i
d
F db k
1
What
version
of
Rdb
are
you
on
now?
1.
What
version
of
Rdb
are
you
on
now?
2.
Are
y
you
physically
p y
y
moving
g
the
database
to
new
storage?
Rdb
on
Integrity
and
Rdb
on
Alpha
Rdb
on
Integrity
and
Rdb
on
Alpha
share
the
exact
same
on
‐
disk
structures
(the
data
is
the
same)
This
means
This
means…
…
if
f
y
you
are
running
g
Rdb
v7.2
on
Alpha
p
and
y
you
are
operating
p
g
in
a
mixed
‐
architecture
Alpha/Integrity
cluster
then…
Congratulations!
In
it’s
simplest
form*
upgrading
to
Rdb
v7 2
is
In
it s
simplest
form ,
upgrading
to
Rdb
v7.2
is
as
easy
as
using
RMU/CONVERT
to
update
the
RDB
root
file
update
the
RDB
root
file.
….Fast!
Done!
Thank you for your time…
(now,
the
small
print…)
*This
assumes
that:
f
What
if
you
are
running
Rdb
v6.1
or
earlier?
What
if
the
database
is
being
physically
moved
to
new
storage?
What
if
the
new
storage
is
not
available
from
the
old
hardware?
1.
How
to
upgrade
Rdb
versions…
I
th
d t
i
About
Software
Concepts
International
LLC
About
Software
Concepts
International,
LLC
Questions
to
Consider
How
to
Upgrade
to
Rdb
V7 2
How
to
Upgrade
to
Rdb
V7.2
Moving
Your
Data
Validating
the
Mo ed
Data
Validating
the
Moved
Data
Cutting
Over
to
New
System
Q
i
d
F db k
Depends on:
Your
prior
version
5.0
and
before
Depends on:
5.1
to
6.1
7.0
to
7.1
Your
prior
hardware
VAX
Alpha
The
chosen
upgrade
method
RMU/CONVERT
or
RMU/BACKUP
&
RESTORE
There
are
multiple
upgrade
options
There
are
multiple
upgrade
options…
1.
RMU/CONVERT
2.
RMU/BACKUP
Æ
RESTORE
3.
SQL
EXPORT
Æ
IMPORT
Rdb 7.2
(Alpha or Integrity)
Rdb 7.0 (VAX or Alpha)
Rdb v7.1 (Alpha)
Rdb v5.1, v6.0 or v6.1
(VAX or Alpha)
Rdb v3.0 – 5.0
(VAX)
1.
Fast
Benefits
1.
Does
not
move
data
to
Limitations
new
storage
2.
Must
follow
Convert
Upgrade
Path
Upgrade
Path
(may
need
intermediate
versions
of
Rdb)
3.
Prior
convert
must
have
1.
Ability
to
move
data
to
Benefits
1.
Time
to
backup
Limitations
y
new
storage
2.
Preserves
prior
database
i
i t t
2.
Time
to
restore
3.
Time
to
move
backup
file
/
version
intact
(assuming
you
do
not
need
to
drop
the
old
database
for
space)
to
new
system/storage
(if
not
available
directly)
5
An
exact
copy
of
the
user
Limitations
Benefits
3
An
exact
copy
of
the
5.
An
exact
copy
of
the
user
storage
areas
(no
improvement)
M t
f ll
R t
3.
An
exact
copy
of
the
user
storage
areas
(no
risk)
6.
Must
follow
Restore
Upgrade
Path
(may
need
intermediate
versions
of
Rdb)
Rdb 7.2
Upgrade and Move
Rdb 7.0 (VAX or Alpha)
Rdb v7 1 (Alpha)
(Alpha or Integrity)
Rdb v5.1, v6.0 or v6.1
(VAX or Alpha)
Rdb v7.1 (Alpha)
Rdb v3.0 – 5.0
(VAX or Alpha)
Benefits
Limitations
1.
Ability
to
move
data
to
new
storage
R t
t
th
d t b
1.
Time
to
export
2.
Time
to
import
2.
Restructures
the
database
(Rebuilds
indexes,
places
data
based
on
current
storage
maps)
Abili
k
h i l
3.
Time
to
move
export
file
to
new
storage
(if
not
available
directly)
3.
Ability
to
make
some
physical
changes
during
the
import
4.
Preserves
prior
version
of
the
(
y)
4.
Storage
space
for
export
4.
Preserves
prior
version
of
the
database
intact
B
fit
Li it ti
1.
Ability
to
move
data
to
new
Benefits
1.
Time
to
unload
Limitations
storage
2.
Restructures
the
database
3
Ability
to
make
physical
and
2.
Time
to
load
3.
Storage
space
for
unload
files
3.
Ability
to
make
physical
and
logical
changes
to
the
database
4.
Loads
of
target
database
may
unload
files
4.
Complexity
start
as
unloads
complete
About
Software
Concepts
International
LLC
About
Software
Concepts
International,
LLC
Questions
to
Consider
How
to
Upgrade
to
Rdb
V7 2
How
to
Upgrade
to
Rdb
V7.2
Moving
Your
Data
Validating
the
Mo ed
Data
Validating
the
Moved
Data
Cutting
Over
to
New
System
Q
i
d
F db k
Is
the
database
being
moved
to
different
storage?
Are
the
old
and
new
systems
part
of
the
same
Are
the
old
and
new
systems
part
of
the
same
OpenVMS
cluster?
If
moving
to
new
storage,
is
the
new
storage
If
moving
to
new
storage,
is
the
new
storage
accessible
to
the
old
system,
if
yes,
how?
Cluster
‐
available
storage
DECnet
1
RMU/BACKUP
Æ
RESTORE
1.
RMU/BACKUP
Æ
RESTORE
2.
SQL
EXPORT
Æ
IMPORT
RMU/UNLOAD
Æ
CREATE
Æ
LOAD
3.
RMU/UNLOAD
Æ
CREATE
Æ
LOAD
4.
HOT
‐
STANDBY
or
“warm
spare”
(Ph i l
AIJ
h
i
i
)
(Physical
AIJ
synchronization)
5.
LOGMINER
(Logical
AIJ
synchronization)
(Logical
AIJ
synchronization)
Key
points:
Key
points:
CONVERTS
are
FAST…
MOVES
l
…MOVES
are
slow
Need
to
MOVE
the
data
to
the
new
system
first,
Move
database
before cutover,
and
apply
transactions
to
database
on
target
storage:
*Applying
AIJs
*Hot
‐
standby
l
d
Logminer +
JCC
loader
At cutover,
apply
final
transactions,
and
f
Rdb
i
Source (old)
Target (new)
system
system
database
AIJ
AIJ
AIJ
AIJ
database
AIJ
AIJ
database
AIJ
AIJ
db
db
RMU-
db
db
RMU-repeat
RMU
/BACKUP
/AFTER
RMU
repeat
database
AIJ
AIJ
AIJ
AIJ
/RECOVER
database
AIJ
AIJ
back
Aij
back
database
AIJ
AIJ
Aij
back
Aij
back
Rdb Hot-standby or
…but, I’m running Rdb v6.1* on my old system,
and Rdb v6.1 is not available on the new system?
Can I still use the “fast move technique?”
Only
Rdb
v7 2
runs
on
Integrity
Only
Rdb
v7.2
runs
on
Integrity
(can’t
apply
AIJs)
M
h
i
i
Must
have
access
to
prior
versions
Cluster
member?
l h
l
One
“creative”
solution
to
this
problem
is
through
the
use
One
creative
solution
to
this
problem
is
through
the
use
of
VAX
or
Alpha
virtualization
software
to
create
a
VAX
or
Alpha
environment
that
runs
on
the
new
Hardware.
VAX or Alpha
Integrity Server
OpenVMS v8.3x
Virtualization
(Software)
Rdb v7.2x
OpenVMS v6.2
Rdb v6 1
Rdb v6.1
Virtual
