Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 14 Oracle Analytics Lounge
- 211 Oracle Analytics News
- 42 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 78 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
[BVT] Oracle Baseline Validation Tool with catalogs in double-byte - migrate from 11.1.1.7 to 12.2.1

When comparing the images with BVT, OPENCV is throwing the following exception.
--------------------
Comparing snapshots[==================================================] 100%Open
CV Error: Assertion failed (j < nimages) in cv::histPrepareImages, file ..\..\..
\..\opencv\modules\imgproc\src\histogram.cpp, line 148
Warning: Error while comparing images: '../../../Results/OBI11g/com.oracle.biee
.bvt.plugin.ui/shared/test01/_portal/dash01/PrompSet-001/あ.png' and '../../../R
esults/OBI12c/com.oracle.biee.bvt.plugin.ui/shared/test01/_portal/dash01/PrompSe
t-001/あ.png'. Ex: CvException [org.opencv.core.CvException: cv::Exception: ..\.
.\..\..\opencv\modules\imgproc\src\histogram.cpp:148: error: (-215) j < nimages
in function cv::histPrepareImages
]
--------------------
Comparing Fails if dashboard path contains multi-byte characters.
It works if dashboard path is single byte characters.
and we have verified that this problem does not occur on Linux OS.
Dashboard path containing Multi-byte characters are not supported in BVT?
Thanks very much for your help in advance, and any reply will be appreciated.
Best Regards,
Answers
-
Hello There ,
Are you running BVT on windows ? if so , this is expected behavior with windows .
Windows has Maximum Path Length Limitation of 260 , hence files longer that this, is not being processed/ fails when running in wondows env
Workaround is : its windows limitation, user can run the BVT on linux to work around this
Same has been confirmed in bug 25121893
Thanks,
Deepali
0 -
Hi Deepali,
I am running BVT on windows.
But Path Length is quite shorter than 260.
So bug 25121893 is not applicable to this problem.
When there is even one multi-byte character, this problem occur.
Best Regards,
0