Inter Media iBeta Testing
on Oracle Database 2003
|
Siste
oppdatert 4.03.2003 av Sofia
Ohlson |
Her er det en del info fra Oracle Beta testing private web site med følgende
liken: http://otnbeta.oracle.com/betaprograms/DB2003/index.htm
En kan logge seg på med brukernavnet sofiao og passordet 1727331.
Så er det mulig opprette sitt eget brukernavn for å besøke siten.
MUSPRO
har fått Beta CSI Number: 19529100
Informasjonen som ligger her er basert på FAQ- dokumentet som er
publisert på overnevnt oracle-siten.
Beta Program new features we want to check
3.
Platform: Sun Solaris v2.8 (64-bit) platform
for the Oracle9i Database Release 2 Beta Program
4.
Feedback to Oracle - Each site will
be asked to complete 1-2 surveys. Oracle also expects sites to be in close
contact with their beta program sponsor.
5. How
long shall we work: Support for the beta program will
end 30 days after production code is available and shipping. Updates will be posted on the beta program
website in the Program News
section.
|
Issues |
Tar
vare på |
|
How
do I schedule time on the iBeta system? We’ll
have 6 concurrent weeks from Monday to Friday. |
SO |
|
One
can finish before 6 weeks – contact the Oracle
Server Technologies Beta Program Office at betaprog_us@oracle.com
to release your system and clean mashin. |
|
|
What features aren’t supported under the
testing: -
Install testing -
Real Application Clusters (RAC) -
Oracle Data Guard SQL Apply or Oracle
Data -
Guard Redo Apply -
Oracle Streams -
Replication -
Benchmarks -
Performance testing, or tests to
scale -
Virtual private database -
Multiple CPU environments. |
|
|
-
What should I do now? -
Prepare your software application
for testing -
Install Oracle client software
required by your application -
Make sure you can connect outside
your firewall (e.g., have a direct connection to the Internet without
proxies) via the Internet using SQL*Net or HTTP connections |
Everybody |
|
Connection to the iBeta system? |
|
|
Data will be secure? |
|
|
What system is provided through iBeta?
|
|
|
Oracle support: If you
identify problems during your beta testing, both Oracle support and
development staff will have access to your iBeta system to diagnose
the problem. If an actual code problem is found, we will also test the fix on
this system when possible. |
|
|
Oracle contact during my testing: log on iTAR, including the host name of the
iBeta server you have been assigned.
|
|
|
No backup and no recover of the corrupted
data during my testing? |
|
|
To load
data into the iBeta database? |
Everybody |
|
To manage
the database: -
Use SQL*Plus via a SQL*Net
connection -
Use iSQL*Plus via an HTTP
connection -
Locally install Enterprise
Manager on your system and remotely manage the database |
Everybody |
|
Database settings on the iBeta server: standard
set-up with the following additional items: - All demo accounts are unlocked -
INTERPRETED Compilation is used -
and the UTF8 character set is used. |
Everybody |
|
To modify the init.ora parameters? |
|
|
It’s not allowed to modify the listener.ora
and tnsnames.ora file on the server? |
|
|
What directory should I store my files in? |
Everybody |
|
Access
level on the iBeta system: -
A dynamic user id and password for
your test session -
This user will be given both SYS
and SYS_ADMIN level access with the following privileges: connect
, resource , dba and sysoper |
|
Christian
Emil Ore, Jon Holmen, Jarle Stabell, Øyvind Bratne, Daniel Ridings and Sofia
Ohlson
We are
declared to check following features of the Beta Program:
1)
Application
Development features vi are interested to test:
|
API &
Pre-Compilers |
Jon,
Daniel, Jarle, Øyvind B. |
|
Java |
Daniel, |
|
Other
Application Development Enhancements |
Everybody |
|
PL/SQL
enhancements |
Everybody |
|
SQL
enhancements |
Everybody |
|
XML
(standards, performance, XML DB, etc) enhancements |
Jarle,
Øyvind |
2)
Content
Management features to test
|
interMedia |
ORDSOURCE
objects – Jon |
|
Text
(search, classification, text search wizards, etc.) |
Cristian
Emil, Daniel |