AnsweredAssumed Answered

Oracle 12c Pluggable and Blackboard

Question asked by jon.messer on Feb 22, 2017
Latest reply on Jan 30, 2018 by af0055432

Like • Show 0 Likes0
Comment • 3

We are in the midst of upgrading our system to Q4 2016 CU 1 and as part of the process wanted to move our database to 12c pluggable. We were successful in doing this in our DEV environment starting with Q2 2016 but when I tried to upgrade to Q4, I got an error message saying we could not use pluggables. We are using SERVICE_NAME instead of SID as that is what our DBAs told us to do. We are reaching out to the community to see if anyone else has experience with 12c pluggables or multi-tenet and Q4 or Q2 and have successfully upgraded using the installer. If you have and are willing to share, we would love the support. Blackboard has indicated this is not supported and is not on the road map to support although 12c is fully supported.

We are running Redhat 6, Java 1.8. Any help is much appreciated!

Thanks,

Jon Messer

Blackboard System Administrator

University of Richmond, VA

1 person has this question

Outcomes

cm0043356 Feb 22, 2017 3:08 PM

Hey Jon,

I don't have a solution necessarily, but thought I would throw this in. We were looking at going 12c pluggable with our upgrade last Summer to Q4 2015. We were connecting with SERVICE_NAME and things seemed to be OK. I forget the exact details, but I think things derailed in our testing when we went to use bbpatch or another utility that didn't play too nicely using service name against a PDB. The below Oracle listener parameter helped us get around that and reconfigure Blackboard back to SID. We ended up not going with pluggable once we heard from Blackboard that it wasn't a supported solution. I think it is a little unclear when you "support 12c" but not its core paradigm shift that will become the norm moving forward. Hopefully we'll see support in a future release.

This year we're looking to move to Q4 2016 but are still sticking with 12.1 single instance rather than CDB/PDB. I'll be curious to see your outcome. Good luck!

Have you messed with this in listener.ora?

USE_SID_AS_SERVICE_listener=on

Current Env: RHEL 6 x64, Oracle 12.1.0.2 Standard, Java 7

Upgrade Env: RHEL 6 x64, Oracle 12.1.0.2 Enterprise, Java 8

Regards,

Chris Moore

Database Administrator

Western Kentucky University

1 person found this helpful

Actions

jon.messer @ cm0043356 on Feb 28, 2017 7:50 PM

Chris,

Thanks. It seems Oracle has extended service of 11g through December 2018 so our DBAs recommended we stick with that one in the hopes that Blackboard might find a way to move their product to 12c pluggables/containers framework. We also are in the process of doing an LMS review which might move us away from Blackboard by Fall 2018. The company is not doing themselves any favors with this. Plus, I upgraded my test environment to Q4 2016 and then CU 1 and could not keep a stable environment. It turns out Blackboard shipped it with a version of Tomcat that is causing a lot of problems. The solution: wait until it becomes unresponsive and restart the entire server. I am sure that is exactly what my university would like for me to do. Anyway, thanks for providing a workaround but since we are getting support from Oracle I was not able to try it.

Jon

1 person found this helpful

Actions

af0055432 Jan 30, 2018 7:16 AM

I understand I'm resurrecting a dead thread, sorry.

We're in the midst of upgrading all of our databases from 11g to 12c, and Blackboard happens to be one of the affected systems. We've failed to upgrade the development server to Q4 2016 CU6 that we've got connected to that 12c environment, due in-part our DBAs using the CDB architecture in the 12c builds.

If anyone is still watching this and has been able to get Blackboard to work with Oracle 12c and the CDB set-up, I would love to hear how.

Current environment:
Blackboard Q4 2016 CU6 (3100.0.6), RHEL6, Oracle 11g

I am planning a service pack upgrade for Blackboard prior to our migration of production to 12c, if by some miracle CDB support has been bundled in Q2 2017 or Q4 2017.

Actions

3 Replies

cm0043356 Feb 22, 2017 3:08 PM
Mark Correct
Correct Answer
Hey Jon,

I don't have a solution necessarily, but thought I would throw this in. We were looking at going 12c pluggable with our upgrade last Summer to Q4 2015. We were connecting with SERVICE_NAME and things seemed to be OK. I forget the exact details, but I think things derailed in our testing when we went to use bbpatch or another utility that didn't play too nicely using service name against a PDB. The below Oracle listener parameter helped us get around that and reconfigure Blackboard back to SID. We ended up not going with pluggable once we heard from Blackboard that it wasn't a supported solution. I think it is a little unclear when you "support 12c" but not its core paradigm shift that will become the norm moving forward. Hopefully we'll see support in a future release.

This year we're looking to move to Q4 2016 but are still sticking with 12.1 single instance rather than CDB/PDB. I'll be curious to see your outcome. Good luck!

Have you messed with this in listener.ora?

USE_SID_AS_SERVICE_listener=on

Current Env: RHEL 6 x64, Oracle 12.1.0.2 Standard, Java 7
Upgrade Env: RHEL 6 x64, Oracle 12.1.0.2 Enterprise, Java 8

Regards,

Chris Moore
Database Administrator
Western Kentucky University
1 person found this helpful
Like • Show 0 Likes0
Actions
- jon.messer @ cm0043356 on Feb 28, 2017 7:50 PM
  Mark Correct
  Correct Answer
  Chris,
  
  Thanks. It seems Oracle has extended service of 11g through December 2018 so our DBAs recommended we stick with that one in the hopes that Blackboard might find a way to move their product to 12c pluggables/containers framework. We also are in the process of doing an LMS review which might move us away from Blackboard by Fall 2018. The company is not doing themselves any favors with this. Plus, I upgraded my test environment to Q4 2016 and then CU 1 and could not keep a stable environment. It turns out Blackboard shipped it with a version of Tomcat that is causing a lot of problems. The solution: wait until it becomes unresponsive and restart the entire server. I am sure that is exactly what my university would like for me to do. Anyway, thanks for providing a workaround but since we are getting support from Oracle I was not able to try it.
  
  Jon
  1 person found this helpful
  Like • Show 0 Likes0
  Actions
af0055432 Jan 30, 2018 7:16 AM
Mark Correct
Correct Answer
I understand I'm resurrecting a dead thread, sorry.

We're in the midst of upgrading all of our databases from 11g to 12c, and Blackboard happens to be one of the affected systems. We've failed to upgrade the development server to Q4 2016 CU6 that we've got connected to that 12c environment, due in-part our DBAs using the CDB architecture in the 12c builds.

If anyone is still watching this and has been able to get Blackboard to work with Oracle 12c and the CDB set-up, I would love to hear how.

Current environment:
Blackboard Q4 2016 CU6 (3100.0.6), RHEL6, Oracle 11g

I am planning a service pack upgrade for Blackboard prior to our migration of production to 12c, if by some miracle CDB support has been bundled in Q2 2017 or Q4 2017.
Like • Show 0 Likes0
Actions

Oracle 12c Pluggable and Blackboard

Outcomes

Related Content

Recommended Content

Incoming Links