Database

Get Involved. Join the Conversation.

Comments

  • Simon Law

    Hi Dragos,

    Similar to the OS user opc, there is no password for oracle.  
    To log in as oracle, you can log in as opc and then switch to oracle using sudo, see here for example.

    If you want to enable SSH private key login for oracle, say using the same key as opc, you can manually replace the oracle authorized keys file in /home/oracle/.ssh/authorized_keys with the one in /home/opc/.ssh/authorized_keys 

    -Simon
       

  • Ram Srinivasan

    Hi:

    Thanks for your reply. Two points to your reply. 

    1. I was creating a new DBCS from the standalone backup. The menu had such an option which is good but it does not work. There was no place for me to provide a Pre-Authenticated Request URL

    2. I see your steps which is more winding. However, please tell me on your step 4 how do I identify the files in object storage corresponding to my backup. They are all chopped up into 100 MB blocks. I have a newly created DBCS. However, it has a database. Can the newly restored database with RMAN have a different name on the same DBCS instance?

  • Ranganath S R

    I check the SR and it seems the Object Storage authentication is failing. Ops thinks that its a password issue.

    That being said, alternative options is

    1 to spin up a new DBCS instance.

    2 Create a File Storage mountpoint.

    3 Mount it on the new DBCS instance.

    4 Download the backup files from Object STorage to File Storage.

    5. Restore using RMAN commands

     

  • Simon Law

    Thanks. I have asked Support to take another look at the SR and reach out to you.

    -Simon

     

  • Ram Srinivasan

    SR 3-20442563411 

    On that SR, to prove that it is not a one-of-a-kind I repeated the whole process from scratch (meaning Oracle 8i DB) and still ended up with that 'unknown error' restoring from standalone backup. 

    What I am asking with this RMAN is my alternative solution. Thanks. 

  • Simon Law

    Hi Ram,

    Can you share the SR number? 

    -Simon

  • Vladislav Uvarov

    The ORA-28860: Fatal SSL error usually indicates an SSL/TLS protocol error rather than an error with the trusted SSL certificate loaded in your Oracle Wallet. Using the free Qualys SSL Test tool, we can see that while this website (https://earthquake.usgs.gov) supports an older TLS 1.0 protocol that is available in all releases of the Oracle Database, it does require the client to support SNI (Server Name Indication) as well:

    This site works only in browsers with SNI support.

    If you are using an older Oracle Database release, the SNI extension for outbound SSL/TLS calls may not be supported. Specifically, there is no SNI support in 11.2 or 12.1 release. One-off patches may be available from My Oracle Support to add SNI support in 12.2 release. All database releases 18c and newer support SNI out of the box. For example, the recently announced APEX in Autonomous Transaction Processing (18c) is able to access this website just fine without any configuration by application developers.

    Hope this helps.

  • Simon Law

    The following suggestion is from the APEX team:

    One technique would be to define REST API(s) for SQL Server DB and then consume them in Oracle.

    Here is an article on how to define the REST API: 
    https://medium.com/voobans-tech-stories/how-to-quickly-create-a-simple-rest-api-for-sql-server-database-7ddb595f751a
     
    Once you have the data coming in JSON format from SQL Server then you should be able to use ORDS to load the data into the Oracle Cloud using DBMS_CLOUD.
     
     
  • Ram Srinivasan

    Thank you Simon

  • Simon Law

    Hi Ram,

    For this particular problem, it's best to contact support, since they have access to the backend environment and can double check if there are any known issues.

    -Simon   

  • Daniel F.

    Hi Mike

    I'm having the same issue. What did you do?

    Cheers

    Daniel

  • Robin Chatterjee

    By the way does OCI actually connect over vnics to storage or is it actually over infiniband ? given that all the hardware is supposed to support infiniband and that the iscsi interface is independant of the public interface I suspect that the storage bandwidth has no relationship to the nic bandwidth.Though I am not sure if this is published anywhere..

    At least in OCI classic I believe it was supposed to match the cloud@customer setup and in that the storage traffic is all over infiniband and not ethernet.

     

  • Robin Chatterjee

    I would assume network bandwidth would have an impact on throughput i.e mbps but not sure how it would relate to iops.

     

    Actually the issue I have is that Oracle caps th iops per block volume to 25,000 iops which is not intuitive. In IaaS i.e normal compute we have the option of choosing the number and size of each block volume to maximise iops for example using a 500GB block size we can attach 32 such volumes for 16 TB of raw storage with 800K iops. if we layer with asm we get 14 tb usable even with triple redundancy ( that cuts write iops by 3 but preserves read iops).

    The problem is with DBCS the number of block volumes is unknown - its beyond our control. all we know is ther must be at least 3 as its triply mirrored and given the table 

    https://docs.oracle.com/en/cloud/paas/database-dbaas-cloud/csdbi/db-deployments.html#GUID-0F42D983-9941-4702-B570-7E308AE50190

    For Oracle Cloud Infrastructure:

    • When creating a deployment: you can create a database of up to 9600 GB (9.3 TB) with backups to both cloud and local storage or up to 16 TB with backups to cloud storage only or no backups.

    • By adding more storage: 28 scale-up operations, each of up to 16 TB, are supported. Thus, the deployment can accommodate a database of up to 158 TB with backups to both cloud and local storage or up to 386 TB with backups to cloud storage only or no backups. However, if you need databases of such large sizes, you should consider using Oracle Database Exadata Cloud Service instead of Oracle Database Cloud Service.

    This does not make it clear what the size of each disk would be...

     

    Oracle Cloud Infrastructure supports 32 block storage volumes attached to a compute node, of which 4 are used when the database deployment is created. Thus, you have 28 opportunities to scale up storage.

    In each scale-up operation, you can create a storage volume of 50 GB to 16384 GB (16 TB) in 50 GB increments. The deployment is put into Maintenance status during the operation

     

    So from this I am surmising that the asm disk size is 50Gb and each block volume added is being sliced up into 50Gb partitions. the problem is that the volume sizes are variable.

     

     

  • Simon Law

    It's not just about storage IOPS, the network of your VM impacts the IOPS and Mbps. For DBCS VM, it has same IOPS as Compute IOPS, check out the different VM shapes and their network bandwidth.   

    https://docs.cloud.oracle.com/iaas/Content/Compute/References/computeshapes.htm#VMShapes

  • Jerry Ursetti

    When you say the user must be REST enabled, are you referring to the steps under Enabling a Schema for SQL Developer Web in the document you referred me to? There's no mention of REST enabling. That document says I need to create a text file containing the password of the user whose schema I want to enable. It then shows creating a file called password.txt in /home/oracle. That's why I mentioned /home/oracle.

    I guess I would follow the steps under Enabling a Schema for SQL Developer Web for each schema user that I want to enable, replacing the password in the text file each time, correct?

    Thanks for your help.