[ZBX-22326] upgrading to 6.2 using oracle for database Created: 2023 Feb 08 Updated: 2023 Feb 09 Resolved: 2023 Feb 09 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Installation (I) |
| Affects Version/s: | 6.2.7 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Trivial |
| Reporter: | charles lomino | Assignee: | Zabbix Support Team |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
production |
||
| Description |
|
Steps to reproduce:
Result: |
| Comments |
| Comment by charles lomino [ 2023 Feb 08 ] |
|
We are migrating from 3.0 to 6.2. We want to continue using oracle for the database. The thought process is to create a new schema for the new version in the same database. A new database account will be created to hit that new schema. Is that a valid approach? |
| Comment by charles lomino [ 2023 Feb 09 ] |
|
I didn't see any response from support on this |
| Comment by charles lomino [ 2023 Feb 09 ] |
|
Lazard has support for this product. I am the responsible party. Albert Li left the firm |
| Comment by Edgars Melveris [ 2023 Feb 09 ] |
|
Please contact the sales team about support contract details - [email protected] |